I am using Ignition v8.1.38, configuring a simple button. Some pre-existing ones have the "Enabled" or "Visible" properties, however when I right-click "remove binding," or select "no binding" the property disappears entirely. I would like to disable the bindings for this without removing the ability to use them entirely for testing purposes.
Are these properties deprecated in future versions and this is why they are being eliminated when I remove bindings?
For example, here are two button instances, one with the Enabled property, the second not.
Check that you are showing all the properties for the button. Drop down at the top of the properties pallet.
1 Like
I think this should be the loading gif for new Vision users
6 Likes
Yes, that's it. Thank you!
I never noticed that filter.
Happens to the best of us.
That burns a lot of people.
It's really tricky if you have the pleasure of supporting the REAL old versions of vision where it didn't save in the "A" filter but that was like 15 or so years ago so you probably won't encounter that problem. I only know of one customer that refuses to upgrade one that old.
What's the client's reason for not upgrading?
15 years ago i was just in Elementary school
Corporate controls everything and someone with power is pushing something else.
2 Likes
Oh, same old sad tale then
Heck, I had an install of FactorySQL running up until a year ago. Easily 15 years.
You can lead a horse to water but you can't make it stop eating trash.
We didn't put that Ignition in. An integrator from Canada did but then he died and we support it.
It's sad they don't go all in on Ignition because the one they use (Plant PAX) is arguably worse than Ignition from 15+ years ago.
Yes, we have a few of those too. It's a workhorse and certainly reliable.
My first project used FactorySQL almost 20 yrs ago and it still works.
1 Like