Persistent Perspective properties and "safe" fallbacks

Ignition
1

For many of our views, we like to save them with persistent properties holding a "safe" fallback value. The properties have bindings that will evaluate in almost every case, but the fallback is there to avoid certain types of UI flickering or bad user displays if the bindings fail or take a long time to finish.

The problem is that every time one of us opens these views in Designer to do anything, those bindings run and the persistent properties are now all holding values relevant to that one case and not the safe fallbacks anymore. It's a pain in the butt adjusting all the properties back before we can hit save.

Does anyone else have this issue? How do you make it less obnoxious?

2

Not sure about the long expression evaluations, but for fails wouldn't you just use the try() expression?

3

Don't make them persistent. Then they'll wake up with a null, for which you can use the coalesce() function to supply the desired startup value.

5 Likes
4

You also then won't have bogus changes recorded against when diffing files.

1 Like