1

Topic: Several "objects" attached to the same GUI tag

You can do lots of advanced graphics with, for example, multiple objects like LEDs attached to the same variable.

But the RemoteXY code builder creates a separate instance of the declaration of the variable, which obviously gets thrown out during compilation.

Please allow separate objects to "share" the variable, without declaring them as multiple variables.

2B, or not 2B, that is the pencil ...

2

Re: Several "objects" attached to the same GUI tag

This requires a lot of work. We plan to separate variables from interface elements. Then you can more flexibly customize your interfaces. You will be able to use the same variable for different interface elements.
The way it is implemented now is very easy for beginners. We would like to leave the way it works now.

3

Re: Several "objects" attached to the same GUI tag

remotexy wrote:

....The way it is implemented now is very easy for beginners..

A beginner would definitely appreciate that multiple objects could be attached to the same variable. That would make drawing dynamic lines (eg flow lines) and boxes (i.e. LEDs) very easy.  As it is you have to have a separate variable for each segment of your line or box drawing, bloating the interface. 

All you have to do is stop  the code generator from duplicating tags (variables), this will allow compilation, will it not? 

As each GUI element is encountered on the code build, just don't create another variable in the output if it already exists.  You are not declaring to which object the variable is attached, it is just a member of the GUI structure.  Yes, this can be eradicated manually by editing the generated code, but if duplicate declarations didn't exist, the beginners would appreciate not having to edit your generated include .....

The interface is already bloated - a 256-state variable for an LED or Pushbutton is overkill. Why can't we have at least BOOL variables, or be able to drill into int8 or int16 tags to the bit level. Now that would be nice !  I'm  all for optimising the data transfer.

2B, or not 2B, that is the pencil ...