Anyway: bacause I need the ability described in previous post, and – in the same time – I want to use Live GUI objects I played a bit with [umenu] and Inspector – now my [umenu] looks more "Ableton style" – not identically, but it’s near enough.
I think it makes some kind of sense, but if you’re dynamically altering attributes of an object, then let’s get serious, you’re probably not going to be automating the value.
For me, this limitation is quite a bother in terms of creating a coherent interface. I have some live.menu and live.numbox objects which I have to mix with standard Max umenu and number boxes just so I can change the ranges and menu items dynamically.
A solution for the live.numbox is to create both a standard Max integer/float number box with transparent border and background which I lay on top of a live.numbox with a transparent font. That way the user controls the standard number box with the live.numbox background. Not ideal, but it works.
As far as the live.menu, it’s probably possible to use scripting to delete the old object and create a new object with the new attributes, but again, that’s obviously not ideal.
I know it’s a long shot, but is there not a possibility to allow an option in the inspector, enable/disabling the ability for automation and thus enabling the use of messages to dynamically alter it’s attributes?