I have technicians reporting that they are needing to double click on a dropdown selection, for it to be accepted, when they previously only had to click their selection once. I did perform and update from 8.1.5 to 8.1.14 two days ago.
Has anyone else experienced a change in the behavior of some dropdowns?
I do not. The component has two bindings, one to a custom parameter that provides the data set and the other that is bound to a tag so it gets updated with the selection. These have not been changed in over a year. We have had issues with the dropdown not closing after a selection is made. Even then, that single click committed the selection and we just had to click outside of the dropdown for it to close.
Would you be able to share a project export of the window that has the dropdown component? We will need to see your specific setup to try to replicate it.
You do your own mental algebra, but at some point its worth asking a subject matter expert for help vs beating your head against a wall. In my experience reports like this have range from user error to a long lived mistake in the PLC programming. Without being about to put eyes on the problem or replicate it there isn’t much that can be done.
Similar to Joe.Miller, walking through upgrading the gateway from 8.1.1 to 8.1.44 and found that now all my dropdowns require a double click versus previously only requiring a single click (via mouse click or touchscreen). Nothing jumps out as to a setting to change it to a different option. No fancy scripting that should have created the change to my knowledge. Has anyone had a similar experience and/or determine a root cause for the change? Thanks
I think I figured it out. It has to do with whether your dropdown is presented as a list or as a table. When you have the dropdown as a list, then it only requires a single click, when it is a Table it is requiring a double click. Not sure that there is a fix for it.
Not sure if anyone within the Ignition software group would like to elaborate here with further details.
Thanks
Email in to our support department (https://support.inductiveautomation.com) and tell them to cross-reference IGN-6473, our internal ticket tracking that bug.