Object visibility in Vision Designer

No way, this was an immediate great thing I noticed when I first started Ignition compared to other packages. Sometimes you have to sandwich things on top of each other with visibility (although I haven't in years), and in Ignition this is completely manageable. In other packages that keep everything visible, it's impossible to mange... I remember in another package having to move the stacked component I wanted to edit to the side so I could actually see it, edit it, then try to get it back to the same spot... worst experience.
The live designer also helps enormously with other parts of developing the GUI as well as it allows you to test while you're developing, rather than having to (compile,) launch the client, and test there.

Layers on the other hand, would be a huge improvement, along with the ability to lock components (looking at you, Perspective).

The Perspective coordinate container grouping experience is very average, so much so that I don't often group things in coord containers; it's just too much hassle. Copying and pasting components into embedded percent coord containers is just horrible since the sizes relate to the coord container you're pasting it into, which are likely wildly different to the one you copied from. I do tend to design using fixed mode though, but having multiple embedded coord containers is a horrible experience as I would want to set these to fixed too, and then you need to remember to set the emdebbed coords and the view coord back to percent once done

4 Likes

I agree with @nminchin

Having a what you see is what you get designer is so much better than legacy development environments.

As other have mentioned I have also used an expression to make the items visible in the designer and putting it into "play" mode will make it look just like it would in the vision client. Best of both worlds.

2 Likes

I would hate forced visibility. I usually put an expression binding on my overlays to hide them in the design environment when I'm not in preview mode, so they're never in the way.

1 Like

I'm not sure about creating bindings for development time; I'd be concerned it would limit scalability. Maybe less of a concern for vision, but for I wouldn't do this for perspective given all sessions are managed by the gateway

I am talking about Vision, so I'm not sure what this means. I simply don't allow an overlay to be visible unless the system flag is greater than one. Otherwise, in Vision, the overlay blocks access to the components in the container.