Button Size and 10-20?

jjames

Is there anyway you can querry a button for its size and location? I'm writing a module for something and I need to know these properties . . . otherwise, for every button that's used in this module, the programmer needs to enter in all this information - not fun.

If we're not capable of doing this now - would be a nice feature eh?

Marc Scheibein

jjames wrote:

Is there anyway you can querry a button for its size and location? I'm writing a module for something and I need to know these properties . . . otherwise, for every button that's used in this module, the programmer needs to enter in all this information - not fun.

If we're not capable of doing this now - would be a nice feature eh?

My first idea was to use the BUTTON QUERY COMMANDS (see software history of any Modero panel). You'll get several information from a button like Opacity, current text, text style etc., but unfortunately not position and size..... You may send a feature request to AMX.

jjames

That's what I thought. I didn't see it in the querry commands - didn't know if someone knew of something . . . "special." Worth a try . . .

DHawthorne

One of the advertised features of Duet was a plug-and-play capability. You plug a new device in, it's detected by the master, and the master automatically downloads whatever support modules it needs to make it run. Aside from the challenge in just that alone, it seems to me to make it viable you would also need a means to have control panel pages and buttons for the new device become available that were not before. So ... wouldn't you need to be able to query existing buttons to know where to place the new without overlap?

Frankly, I will be surprised if that kind of capability actually pans out in reality. No matter how hard you try to anticipate future equipment and be ready for it, something will eventually comes along that defeats you. I am not very much of a fan of trying to make the equipment smarter than the technician (who here has never had trouble with a projector automatically sensing a signal and switching into a state you did not want it to??). I think the current paradigm of making your code modular and adding new devices manually is adequate. But if you really need a dynamic system, you really need a way to detect current states.