Home › Microsoft Streets and Trips › Free add-ons for Microsoft Streets and Trips › S&T Keys for Streets & Trips 2010 Bugs Report
The S&T Keys "Menu F4" button is positioned over the MSFT OSK (if in use) which creates a conflict with the underlying keyboard buttons. It would be nice if the Menu F4 button was just over the map. Even if it were in the upper left hand corner...
The Menu panel pop-up is just a little bit wide for use on my Viliv S5 when in 270-degree portrait mode.
Is there any chance the panel's width could be reduced a few pixels? For instance, the space between the two columns of buttons is luxuriously wide, perhaps a few pixels could be given up from that space.
If this is a major programming hassle, don't bother.
Is there any chance the panel's width could be reduced a few pixels? For instance, the space between the two columns of buttons is luxuriously wide, perhaps a few pixels could be given up from that space.
If this is a major programming hassle, don't bother.
SpadesFlushsaid:
It is supposed to be just over the map...
Please add a screenshot because it is not possible for me to figure out
Quote:
The S&T Keys "Menu F4" button is positioned over the MSFT OSK (if in use) which creates a conflict with the underlying keyboard buttons. It would be nice if the Menu F4 button was just over the map.
Please add a screenshot because it is not possible for me to figure out
SpadesFlush said:
If you can add a screenshot, again it would help me to understand what is the problem...
Quote:
Is there any chance the panel's width could be reduced a few pixels? For instance, the space between the two columns of buttons is luxuriously wide, perhaps a few pixels could be given up from that space.
SpadesFlush, I would help you with a screenshot of the menu width thing but I can't get the HP to duplicate it. I can only get to 720x1280 and the menu still fits. Are you running 600x1024?
I can't help with the OSK one as this tablet is running Vista and the built-in OSK is way more flexible than XP.
Terry
I can't help with the OSK one as this tablet is running Vista and the built-in OSK is way more flexible than XP.
Terry
Quote:
Originally Posted by SpadesFlush
The Menu panel pop-up is just a little bit wide for use on my Viliv S5 when in 270-degree portrait mode.
Is there any chance the panel's width could be reduced a few pixels? For instance, the space between the two columns of buttons is luxuriously wide, perhaps a few pixels could be given up from that space.
If this is a major programming hassle, don't bother.
Is there any chance the panel's width could be reduced a few pixels? For instance, the space between the two columns of buttons is luxuriously wide, perhaps a few pixels could be given up from that space.
If this is a major programming hassle, don't bother.
Quote:
Originally Posted by SpadesFlush
The S&T Keys "Menu F4" button is positioned over the MSFT OSK (if in use) which creates a conflict with the underlying keyboard buttons. It would be nice if the Menu F4 button was just over the map. Even if it were in the upper left hand corner...
With regard to the F4 button, I think it is caused by the fact that the OSK appears over the map, rather than forcing S&T to resize to accommodate the OSK window. This is OK with me if the F4 button would not be over top of the OSK.
Quote:
Originally Posted by tcassidy
SpadesFlush, I would help you with a screenshot of the menu width thing but I can't get the HP to duplicate it. I can only get to 720x1280 and the menu still fits. Are you running 600x1024?
...
...
Terry, I see in your screenshot the same issue as what I have in mine. That is the caption "GPS Pause" half way down the left column is cut off on the left because there is not enough margin.
So, it's not just me.
So, it's not just me.
Quote:
Originally Posted by SpadesFlush
With regard to the F4 button, I think it is caused by the fact that the OSK appears over the map, rather than forcing S&T to resize to accommodate the OSK window. This is OK with me if the F4 button would not be over top of the OSK.
You could drag the keyboard up higher away from the F4 icon.
Terry
Quote:
Originally Posted by SpadesFlush
Terry, I see in your screenshot the same issue as what I have in mine. That is the caption "GPS Pause" half way down the left column is cut off on the left because there is not enough margin.
So, it's not just me.
So, it's not just me.
Terry
Ok i can see now. It is always true that a picture worth a thousand words.
1- For the menu width, i will try to squeeze in the horizontal direction as much as possible...
2- For the F4 button issue, it is because the button appears at the left bottom corner of the S&T map on the screen. If you cover it with anything else, there is no easy way to find this. What make it more complicated is that user can use any custom OSK i cannot imagine with different look. So very difficult to deal with that one. If most user prefer to have the OSK at the bottom of the screen, i can swapt the F4 touch button to the upper left instead of bottom left, or make the position configurable. This is the easiest solution i can see. Probably configuration for the button position (at least two choices bottom and top left), would be my actual proposal (with top left the new default button position?)...
What do you think of this?
1- For the menu width, i will try to squeeze in the horizontal direction as much as possible...
2- For the F4 button issue, it is because the button appears at the left bottom corner of the S&T map on the screen. If you cover it with anything else, there is no easy way to find this. What make it more complicated is that user can use any custom OSK i cannot imagine with different look. So very difficult to deal with that one. If most user prefer to have the OSK at the bottom of the screen, i can swapt the F4 touch button to the upper left instead of bottom left, or make the position configurable. This is the easiest solution i can see. Probably configuration for the button position (at least two choices bottom and top left), would be my actual proposal (with top left the new default button position?)...
What do you think of this?
About the F4 button issue covered by the OSK...
Ok I have thought about it a little. The OSK is using a lot of screen space and should be used only if necessary. There are already S&T Keys features to deal with this. S&T Keys is able to popup popdown your OSK automatically when needed.
Scenario:
1- Entering a destination to create a new route. Use the <END> hotkey or <F4> with END touch screen (destination) button. Configure in figure 12 (see S&T Keys 2009 online manual link in my signature to see all figures I am talking about) the option to deal with the OSK when using the END button. This will popup when it is time to enter the destination in the find window and popdown the OSK when not needed.
2- Click the option in figure 11b and 11c to popup the OSK when a favorite destination need to be enter
3- Configure in fig 12 your needed On Screen Keyboard if not using default window OSK.
4- In figure 7, configure to use the zoom touchscreen keys and F4 touch screen key
5- All other S&T major operations can be controlled through F4 popup menu of S&T Keys by pressing the touchscreen F4 button then pressing the needed button on F4 touchscreen menu (see fig 3)
So in all other cases, the OSK is not needed to operate S&T when using S&T Keys configured correctly as specified above. Better it will deal with the OSK and will popit onscreen only when needed, so you always have maximum screen size to see S&T map. Also when letting S&T Keys dealing with the OSK itself, you are not supposed to ever see the F4 button in your way...
Correct me if i am wrong (cause i don't use a touchscreen myself), but there are not supposed to be many cases that you need to popup OSK from F4 menu manually when configured as above (and in this situation the F4 button could be in your way through the OSK)?
Maybe only S&T F3 function is the major missing through F4 popup (but it can be simulated much slowlier with the S&T Keys F5 navigate touchscreen key)...
Ok I have thought about it a little. The OSK is using a lot of screen space and should be used only if necessary. There are already S&T Keys features to deal with this. S&T Keys is able to popup popdown your OSK automatically when needed.
Scenario:
1- Entering a destination to create a new route. Use the <END> hotkey or <F4> with END touch screen (destination) button. Configure in figure 12 (see S&T Keys 2009 online manual link in my signature to see all figures I am talking about) the option to deal with the OSK when using the END button. This will popup when it is time to enter the destination in the find window and popdown the OSK when not needed.
2- Click the option in figure 11b and 11c to popup the OSK when a favorite destination need to be enter
3- Configure in fig 12 your needed On Screen Keyboard if not using default window OSK.
4- In figure 7, configure to use the zoom touchscreen keys and F4 touch screen key
5- All other S&T major operations can be controlled through F4 popup menu of S&T Keys by pressing the touchscreen F4 button then pressing the needed button on F4 touchscreen menu (see fig 3)
So in all other cases, the OSK is not needed to operate S&T when using S&T Keys configured correctly as specified above. Better it will deal with the OSK and will popit onscreen only when needed, so you always have maximum screen size to see S&T map. Also when letting S&T Keys dealing with the OSK itself, you are not supposed to ever see the F4 button in your way...
Correct me if i am wrong (cause i don't use a touchscreen myself), but there are not supposed to be many cases that you need to popup OSK from F4 menu manually when configured as above (and in this situation the F4 button could be in your way through the OSK)?
Maybe only S&T F3 function is the major missing through F4 popup (but it can be simulated much slowlier with the S&T Keys F5 navigate touchscreen key)...
tcassidy said:
The instructions at left of buttons is more for keyboard users who want to know on which keyboard key to press to do the function (when no touchscreen or pointing device is available)
Touchscreen users are more interested in the info located inside the button they need to click. It should be sufficient to tell everything needed for the function usage. What is written to the left of the button (keyboard key) is not usefull for them?
Quote:
But the button captions should make it clear what the function is. Do you need the separate instructions on the left? It is sort of like the letters to the left of the other set of buttons...not really required as they are duplicated on the buttons.
Touchscreen users are more interested in the info located inside the button they need to click. It should be sufficient to tell everything needed for the function usage. What is written to the left of the button (keyboard key) is not usefull for them?