Focusing & Function Keys
Posted: Wed 14 Aug 2013, 02:13
Hi greengeek and All,
Considering moving the Function Keys to the keypad as a possible remedy for target applications obscuring the keyboard, I turned Function Keys off using xvkbd's menu. Although examining the config file for xvkbd's strip keyboard indicates that function keys can be assigned to the keys on the keypad, doing so and turning the keyboard function keys off won't alleviate the overlap problem. The remaining keys on the keyboard increase in size vertically so that the keyboard occupies the same screen-space.
But in exploring the 1Switch keyboard again I think there can be some improvement. Although, in building a keyboard I use the computer's built-in keyboard and mouse, I always test the results using radar. Radar, in xvkbd-linear mode, begins its automatic scroll pattern at the left top corner. I placed the spacebar there reasoning that it would be one of the most frequently used keys. I now wonder if radar's default timing provides sufficient opportunity to press the "button" before the cursor will have scrolled below top row. And, if the spacebar isn't the "first" key, what key would you recommend as the first key?
I placed an Esc Key on each row. Pressing the "button" while the cursor is over an Esc key does nothing other than returning the cursor to the start of its scroll pattern. Esc keys enable easy recovery if the cursor is scrolling on the wrong row. Most are near the end of their rows, so also serve to return the cursor to the start of the pattern rather than allowing the cursor to scroll beyond the keyboard and enduring the time it would take to re-enter xvkbd mode. But, I wonder if they might be better placed near the middle of the row? Perhaps a "Beginner's" keyboard until the user becomes familiar with the characters appearing on each row. I know I had to "Esc" several times having "missed" the correct row, or having pressed the "button" too soon, starting the right-ward scroll on the wrong row.
Can either of these concerns be handled through adjustments in radar's config file? Frankly, I'm not certain what each parameter is supposed to accomplish?
Regarding having to focus on a target application rather than respond to a mis-directed keypress: Radar's toggle works well to change focus. It takes far less time to send a "backspace" to erase a misplaced keypress followed by radar's toggling to the desired target, than maneuvering to the focus key, then allowing the mouse-cursor to scroll off the keyboard, manually directing the cursor onto the desired target application's title bar, sending a keypress and then re-entering xvkbd mode to begin commence typing.
mikesLr
Considering moving the Function Keys to the keypad as a possible remedy for target applications obscuring the keyboard, I turned Function Keys off using xvkbd's menu. Although examining the config file for xvkbd's strip keyboard indicates that function keys can be assigned to the keys on the keypad, doing so and turning the keyboard function keys off won't alleviate the overlap problem. The remaining keys on the keyboard increase in size vertically so that the keyboard occupies the same screen-space.
But in exploring the 1Switch keyboard again I think there can be some improvement. Although, in building a keyboard I use the computer's built-in keyboard and mouse, I always test the results using radar. Radar, in xvkbd-linear mode, begins its automatic scroll pattern at the left top corner. I placed the spacebar there reasoning that it would be one of the most frequently used keys. I now wonder if radar's default timing provides sufficient opportunity to press the "button" before the cursor will have scrolled below top row. And, if the spacebar isn't the "first" key, what key would you recommend as the first key?
I placed an Esc Key on each row. Pressing the "button" while the cursor is over an Esc key does nothing other than returning the cursor to the start of its scroll pattern. Esc keys enable easy recovery if the cursor is scrolling on the wrong row. Most are near the end of their rows, so also serve to return the cursor to the start of the pattern rather than allowing the cursor to scroll beyond the keyboard and enduring the time it would take to re-enter xvkbd mode. But, I wonder if they might be better placed near the middle of the row? Perhaps a "Beginner's" keyboard until the user becomes familiar with the characters appearing on each row. I know I had to "Esc" several times having "missed" the correct row, or having pressed the "button" too soon, starting the right-ward scroll on the wrong row.
Can either of these concerns be handled through adjustments in radar's config file? Frankly, I'm not certain what each parameter is supposed to accomplish?
Regarding having to focus on a target application rather than respond to a mis-directed keypress: Radar's toggle works well to change focus. It takes far less time to send a "backspace" to erase a misplaced keypress followed by radar's toggling to the desired target, than maneuvering to the focus key, then allowing the mouse-cursor to scroll off the keyboard, manually directing the cursor onto the desired target application's title bar, sending a keypress and then re-entering xvkbd mode to begin commence typing.
mikesLr