Yes, I know but that’s not the point.
The point is that is taking them (IA) so long (years) to fix something basic as the button component which is IMNSHO the most essential component of every user interface.
Agreed. However, I’m not sure discussing on this forum is going to do much good. You need to get with your sales rep and voice complaints. Keep them coming on a weekly basis and the more people that complain the better chance it will be fixed sooner. I feel your frustration as I have gone through the same thing on other issues.
Start an idea on the ideas site and link to it from here so we can up vote it. The more votes, the higher its priority
It’s been 9 months since I first complained about this and I just upgraded to version 8.1. Posting on this forum hasn’t helped me or anyone else on this thread. I still have an open ticket with support and while the support tech agree its a problem they haven’t been able to expedite a solution either. Today I will report it to my sales rep (per jlandwerlen’s suggestion) and see what happens.
1 Like
Hi all. I totally understand the frustration here.
This issue is part of a collection of UI issues that we are working to coordinate fixes for with the provider of our Swing Look & Feel. I know it is frustrating upgrading and hoping this is fixed, only to find that it is not. All I can do at this point is assure you that our attention is focused in this direction right now, so you should see action soon. I will update this thread when there is tangible movement on this, including once I have some better time-frame information.
r.popeszku, I don’t know if you’ve reached out to your sales rep yet, but if not, you can probably skip it. All they’re going to do is come talk to me, and I’m already aware.
4 Likes
Yep, I reached out to Shaun today and he is the one who helped escalate the problem to you. I think everyone has been waiting a long time for a solution to this issue and I am glad you are looking into it.
Rudy
Curious if there has been any progress made on this issue?
It’s not fixed and released yet, but yes we’ve made progress towards getting a whole collection of UI Look and Feel problems fixed.
2 Likes
Thanks for the quick response!
Not to nerco an old thread, but did this get fixed? Still feels like an issue.
New to ignition (but doing controls for a bit).
If I change the background of a button to not be blue (sorry, buttons should be grey), when I disable the button (Uncheck enable) I lose the dynamic effect of the button being muted.
I feel this is similar to the original posters issue. How do I go about muting a button if I don't want it to be blue? Do I need to create a custom style for enable/not-enabled? Or there a way to update the base enabled style?
Vin
Are referring to Perspective?
Yes. 8.1.44
I was able to get by with a style class and changed the alpha from there and it's working. Now just wonder if this will ever get broken in an application upgrade in the future.
This is a vision related issue that does not affect perspective elements or styles as they are built with React not swing.
But I typically have an enabled and disabled button class and if the button is enabled, I have a binding that appends the enabled class or the disabled class if it is disabled.
1 Like
If you want gray buttons as default, can you use the secondary button instead of a primary button? The default disabled button style works with this without a custom style.
1 Like
I had looked at that as well. But on my application the secondary buttons were white and behaved the same as the primary when I tried to update the BG colour.
I have a custom style class for just buttons and have them applied to all buttons. Basically created what Benjamin noted.
Just odd that the default button, when you enable or disable it, the button style changes as you expect, but when assigning a "custom" colour for for the base button or text and disable the button, the feature that once worked, just doesn't.
Just to be clear, the secondary buttons are not white, they are #FAFAFA (--neutral-10).