Hello,
I wanted to share some feedback regarding a usability issue in the new version of Ignition when editing configurations in the Gateway pages.
The “Changes saved” popup/tooltip that appears in the top-right corner of the screen often covers important main buttons.
For example, when I edit my security levels configuration, I save, then realize I forgot an option. I check the option, but then I have to wait more than 5 seconds for the popup to disappear before I can click the “Save Changes“ button hidden behind it.
Here are at least two routes where I noticed this behavior:
- /app/platform/system/gateway/settings
- /app/platform/security/levels
This can be frustrating when making quick adjustments, as it interrupts the workflow. Just sharing this observation in case it’s useful for future improvements.
This is a well-known issue internally, and we have a high-priority ticket to improve this behavior. We’re not sure of the timeline for this improvement, but if it doesn’t make release it will be in an early version of 8.3.
2 Likes
I’m with e.sagnelonge. For me it is about installing multiple modules in one sitting. Thanks for making this high priority.
I wanted to take a moment to keep everyone here updated.
Moving the Toasts is going to require more internal discussion than we had time for leading into 8.3.0, so we won’t be moving the Toasts before that time. We do recognize that the Toasts currently obscure the action button, and we can improve this without changing their position. We’ve made all toasts dismissible and reduced their display time from 5 seconds to 3.
This should hopefully get them out of your way before you need to use that button again, or at the very least give you a way to remove them yourself.
As for future efforts to move them, the original direction was to move them more toward the “middle” of the right side of the viewport; down away from the singleton call-to-action button, but above the non-singleton call-to-action button. There are concerns with this approach however because we would no longer be impacting singleton creation/save, but we would begin impacting interaction with datagrid rows.
