Panel Input Considerations
-
I created a video for this because it's easier to explain through demonstration. It has audio, you have been warned.
Video: https://1drv.ms/v/s!AuWHX0h5bAoRiqYlhpum3onId3dGlw?e=QISBkG
In short:
-
Being able to use the Escape key on a text field to get out is panel input in general for easier maneuverability across the interface is important.
-
When Defocusing from a panel using the mouse, it should deactivate input in that field altogether upon return. Moreover, it should autoupdate it from whatever the user had left in before moving on. Maybe reverting is better with some testing, but I'm leaning towards auto update so perhaps the user can be move around the interface more easily
There's other little issues that I picked up on video that need checking. Hopefully that is of help. If y'all have other ideas about how to improve panel input, feel free to use this post to branch off into other considerations.
-
-
@debraspicher I added this to the backlog.
-
@debraspicher said in Panel Input Considerations:
Moreover, it should autoupdate it from whatever the user had left in before moving on.
When a panel is defocused from an input field, the value of that field is applied automatically.
If this is not the case, then there is a bug. Is there a field where this did not happen?
-
@VectorStyler The criticism was that it wasn't deactivating the field input together when clicking away from that panel, not that it didn't have that outcome (edit: Though I can see why that's unclear). It should ideally do that when clicking off somewhere in VS and it shouldn't be reactivated for input when moving back to that specific panel. But looking at the video, it could be a matter of an extended click zone for the type size field in particular in the Character Panel. I clicked in between the word Leading and Kerning (in-between those field labels) and it reactivated the type size area just now in testing...
Other areas of the interface are like this that when looking for dead space to focus panels or dialogs, it reactivates areas for input. It creates friction because it often is a habit with many users to either Escape or close out input by clicking white space in panels, etc. Edit: In most cases (if not all), it's usually input fields that take keyboard entry, aka text, that causes the most slowdown in this way.
