Hi,
I'd like to see the keyboard interface improved. There are a few issues right now that make it not a great experience.
I'd like to acknowledge, yes, Masso is not a PC OS but an embedded system whom emulates a PC style mouse and keyboard driven UI. Standard conventions for UI interaction should be followed, even for an embedded system.
1: Keyboard repeat - this is a standard expected feature where keyboard is used to interact with any computer/hmi/etc. You have no keyboard repeat.
2: Typing speed is a problem - type too fast and you get repeated chars that you don't want. This is dangerous for MDI if you don't notice. Your feed rate could go from 100 to 1100, or commanded distance could go from 50 to 500. Recipe for crashed machine, broken tools, damaged parts.
3: Continuous jogging on the keyboard does not work, even when you have continuous mode selected. I suspect this is related to the way you handle the keyboard interface (polled instead of interrupt driven?)
4: Remove dependence on the mouse as much as possible. If you can do things like set focus to the password box when that pops up instead of forcing the user to reach for the mouse; allow tab to be used to get between field and arrow keys to be better used to move between UI elements (the setup screen is terrible for this). Again, look at how any modern PC OS is setup - you can use shortcut keys, tab, arrow keys, etc to move between all UI elements for a faster more convenient experience.
Cheers!
Shaun
I'd like to see the keyboard interface improved. There are a few issues right now that make it not a great experience.
I'd like to acknowledge, yes, Masso is not a PC OS but an embedded system whom emulates a PC style mouse and keyboard driven UI. Standard conventions for UI interaction should be followed, even for an embedded system.
1: Keyboard repeat - this is a standard expected feature where keyboard is used to interact with any computer/hmi/etc. You have no keyboard repeat.
2: Typing speed is a problem - type too fast and you get repeated chars that you don't want. This is dangerous for MDI if you don't notice. Your feed rate could go from 100 to 1100, or commanded distance could go from 50 to 500. Recipe for crashed machine, broken tools, damaged parts.
3: Continuous jogging on the keyboard does not work, even when you have continuous mode selected. I suspect this is related to the way you handle the keyboard interface (polled instead of interrupt driven?)
4: Remove dependence on the mouse as much as possible. If you can do things like set focus to the password box when that pops up instead of forcing the user to reach for the mouse; allow tab to be used to get between field and arrow keys to be better used to move between UI elements (the setup screen is terrible for this). Again, look at how any modern PC OS is setup - you can use shortcut keys, tab, arrow keys, etc to move between all UI elements for a faster more convenient experience.
Cheers!
Shaun
