Home › Microsoft Streets and Trips › Free add-ons for Microsoft Streets and Trips › S&T Keys for Streets & Trips 2010 Bugs Report
Mister,
The OSK really only comes into play for typing in an address or somewhere to find; you are entirely correct that the Keys buttons cover most of the commands.
Your S&T Keys' default OSK is the MSFT one which is fine. I think it is consistent to lay out your Menu with that in mind rather than allow for various unknowable other OSK options.
I like the OSK at the bottom of the screen the way you have it in the Beta.
In response to your question about the F4 button location, I would prefer the upper left corner even if it did not conflict with the OSK. It is more in touch with the usual placement for command function buttons. I plan to hide all the tool bars I can when using S&T Keys to save screen real estate, so it would be logical to have the F4 button where I would normally expect to see tool bars.
These are just my preferences. Keys is really excellent as it is; you have done a terrific job with it and I wouldn't want you to torture yourself overly on these mini considerations.
The OSK really only comes into play for typing in an address or somewhere to find; you are entirely correct that the Keys buttons cover most of the commands.
Your S&T Keys' default OSK is the MSFT one which is fine. I think it is consistent to lay out your Menu with that in mind rather than allow for various unknowable other OSK options.
I like the OSK at the bottom of the screen the way you have it in the Beta.
In response to your question about the F4 button location, I would prefer the upper left corner even if it did not conflict with the OSK. It is more in touch with the usual placement for command function buttons. I plan to hide all the tool bars I can when using S&T Keys to save screen real estate, so it would be logical to have the F4 button where I would normally expect to see tool bars.
These are just my preferences. Keys is really excellent as it is; you have done a terrific job with it and I wouldn't want you to torture yourself overly on these mini considerations.
SpadesFlush said:
It is not for torture, it is just for fun
I'll see what i can do with that...
Thanks
Quote:
These are just my preferences. Keys is really excellent as it is; you have done a terrific job with it and I wouldn't want you to torture yourself overly on these mini considerations.
I'll see what i can do with that...
Thanks
SpadesFlush:
About the F4 touchscreen menu button position:
After some tests, it appears to be very difficult to do a clean job at positionning the F4 button in top left or top right of map screen. This is related to behavior of the map that change between fullscreen/normal mode, as an example in FS there is a top popup (when the mouse is moving) that moves sometimes over the map, sometimes squeezing the map. There is also sometime the status compass bar, sometimes not. So the F4 button could not go at top of the map (to not interfere with S&T) but should be somewhere in between middle and top with a risk to touch the zoom buttons when the map is squeeze. It would not look very nice neither. For this reason, i will add a configuration option for F4 button position to be bottom left or bottom right. These are very easy to achieve. I am not sure that this would help much with the OSK being covered by F4 button.
Another solution would be to set OSK to be "Top Most window", so F4 S&T Keys button would go below it in all cases when popup. By configuring S&T Keys to control the OSK automatically as i explained in previous post, this should deal with most of the problems i guess (and when OSK popup set as top most window, this will always certify that if the F4 button is onscreen, it would be below the OSK maybe but never on top of it)...
About S&T Keys screen needed resolution:
I have resized everything so now any screen resolution of at least 600 pixels vertical and horizontal would allow to see all S&T Keys menus correctly. So it will allow to use it on much more devices with widescreen displays or portrait mode devices than actually with previous versions. This will be done in the next beta version...
About the F4 touchscreen menu button position:
After some tests, it appears to be very difficult to do a clean job at positionning the F4 button in top left or top right of map screen. This is related to behavior of the map that change between fullscreen/normal mode, as an example in FS there is a top popup (when the mouse is moving) that moves sometimes over the map, sometimes squeezing the map. There is also sometime the status compass bar, sometimes not. So the F4 button could not go at top of the map (to not interfere with S&T) but should be somewhere in between middle and top with a risk to touch the zoom buttons when the map is squeeze. It would not look very nice neither. For this reason, i will add a configuration option for F4 button position to be bottom left or bottom right. These are very easy to achieve. I am not sure that this would help much with the OSK being covered by F4 button.
Another solution would be to set OSK to be "Top Most window", so F4 S&T Keys button would go below it in all cases when popup. By configuring S&T Keys to control the OSK automatically as i explained in previous post, this should deal with most of the problems i guess (and when OSK popup set as top most window, this will always certify that if the F4 button is onscreen, it would be below the OSK maybe but never on top of it)...
About S&T Keys screen needed resolution:
I have resized everything so now any screen resolution of at least 600 pixels vertical and horizontal would allow to see all S&T Keys menus correctly. So it will allow to use it on much more devices with widescreen displays or portrait mode devices than actually with previous versions. This will be done in the next beta version...
Quote:
Originally Posted by MisterMoonlight
SpadesFlush:
About the F4 touchscreen menu button position:
After some tests, it appears to be very difficult to do a clean job at positionning the F4 button in top left or top right of map screen. This is related to behavior of the map that change between fullscreen/normal mode, as an example in FS there is a top popup (when the mouse is moving) that moves sometimes over the map, sometimes squeezing the map. There is also sometime the status compass bar, sometimes not.
About the F4 touchscreen menu button position:
After some tests, it appears to be very difficult to do a clean job at positionning the F4 button in top left or top right of map screen. This is related to behavior of the map that change between fullscreen/normal mode, as an example in FS there is a top popup (when the mouse is moving) that moves sometimes over the map, sometimes squeezing the map. There is also sometime the status compass bar, sometimes not.
Quote:
So the F4 button could not go at top of the map (to not interfere with S&T) but should be somewhere in between middle and top with a risk to touch the zoom buttons when the map is squeeze. It would not look very nice neither. For this reason, i will add a configuration option for F4 button position to be bottom left or bottom right. These are very easy to achieve.
Quote:
I am not sure that this would help much with the OSK being covered by F4 button.
Another solution would be to set OSK to be "Top Most window", so F4 S&T Keys button would go below it in all cases when popup. By configuring S&T Keys to control the OSK automatically as i explained in previous post, this should deal with most of the problems i guess (and when OSK popup set as top most window, this will always certify that if the F4 button is onscreen, it would be below the OSK maybe but never on top of it)...
Another solution would be to set OSK to be "Top Most window", so F4 S&T Keys button would go below it in all cases when popup. By configuring S&T Keys to control the OSK automatically as i explained in previous post, this should deal with most of the problems i guess (and when OSK popup set as top most window, this will always certify that if the F4 button is onscreen, it would be below the OSK maybe but never on top of it)...
Quote:
About S&T Keys screen needed resolution:
I have resized everything so now any screen resolution of at least 600 pixels vertical and horizontal would allow to see all S&T Keys menus correctly. So it will allow to use it on much more devices with widescreen displays or portrait mode devices than actually with previous versions. This will be done in the next beta version...
I have resized everything so now any screen resolution of at least 600 pixels vertical and horizontal would allow to see all S&T Keys menus correctly. So it will allow to use it on much more devices with widescreen displays or portrait mode devices than actually with previous versions. This will be done in the next beta version...
Again, I really appreciate all the effort you are putting into this.
Mr Moonlight,
First of all - THANKS!!! S&T hotkeys is working!!! I've programmed my mouse to use left and right clicks for F6 (insert pushpin at current location) and Insert (toggle GPS trail). Now, while driving I can simply click a mouse button to start and stop the GPS trail as needed, and to insert a pushpin at current location. As far as I can tell, the program works as intended, except for one thing that may or may not be related to S&T hotkeys.
While driving and the GPS trail is on, I can see the trail is correctly tracking where I'm at. I can verify the accuracy of the route by overlaying the saved .GPX file in Google Earth or ArcView - the route is very accurate, at least accurate enough for my purposes.
What's strange is when I use the F6 key to insert pushpin at current location, the pushpin is inserted, but the pushpin accuracy is pretty bad, especially compared to the GPS trail (I would think the accuracy of the GPS trail and the pushpin location would be identical?). Most of the time the pushpin is inserted 60'-140' off the GPS route line - in one instance it was inserted 430' off the route line. Please see this image file that clearly shows this. This image is from ArcView, but it looks the same in Google Earth, and the pushpin location is clearly off the route path in S&T as well, just not as obvious without the imagery in the background.
Please note that I realize pushpin accuracy while driving/moving is prone to errors for obvious reasons. so each time I inserted a pushpin the car was completely stopped, and it was still way off from what the GPS trail was currently tracking. Also, the "Provide Navigation" box was NOT checked, so routing was not being "snapped" to roads. As far as I know the GPS trail is what the GPS receiver was actually picking up and it's fine, I just need the pushpins to better fall in line with the GPS trail.
First of all - THANKS!!! S&T hotkeys is working!!! I've programmed my mouse to use left and right clicks for F6 (insert pushpin at current location) and Insert (toggle GPS trail). Now, while driving I can simply click a mouse button to start and stop the GPS trail as needed, and to insert a pushpin at current location. As far as I can tell, the program works as intended, except for one thing that may or may not be related to S&T hotkeys.
While driving and the GPS trail is on, I can see the trail is correctly tracking where I'm at. I can verify the accuracy of the route by overlaying the saved .GPX file in Google Earth or ArcView - the route is very accurate, at least accurate enough for my purposes.
What's strange is when I use the F6 key to insert pushpin at current location, the pushpin is inserted, but the pushpin accuracy is pretty bad, especially compared to the GPS trail (I would think the accuracy of the GPS trail and the pushpin location would be identical?). Most of the time the pushpin is inserted 60'-140' off the GPS route line - in one instance it was inserted 430' off the route line. Please see this image file that clearly shows this. This image is from ArcView, but it looks the same in Google Earth, and the pushpin location is clearly off the route path in S&T as well, just not as obvious without the imagery in the background.
Please note that I realize pushpin accuracy while driving/moving is prone to errors for obvious reasons. so each time I inserted a pushpin the car was completely stopped, and it was still way off from what the GPS trail was currently tracking. Also, the "Provide Navigation" box was NOT checked, so routing was not being "snapped" to roads. As far as I know the GPS trail is what the GPS receiver was actually picking up and it's fine, I just need the pushpins to better fall in line with the GPS trail.
waveguide:
If i remember correctly, F6/F10 functions are not compatible with Streets & Trips gps trail feature. If i remember correctly, there is code to keep this feature from attempting to work when the gps trail is active (maybe this prevention mechanism is not working correctly). I will confirm to you later, but i think that the gps trail is red and will keep these functions from working correctly. This is the same problem with any red icons you may insert on the map or any red POI category. The latest v2.55.2 beta has an extra function to help a little when other red items are on the map, but the actual algorithm for GPS icon search is simple to avoid taking too much time to detect the GPS (that could be moving)
Here an extract of S&T Keys 2009 about F6 function:
So if you have time before i test it myself, you can do some tests without using the gps trail to see if it improves things...
For curiosity, did you try this feature with version 2.55.1 or 2.55.2?
Are you driving fullscreen navigation or not while using?
What kind of computer/os you have (with memory?)?
In a specific situation where you press the F6 key, was the GPS icon was stable on the screen?
If i remember correctly, F6/F10 functions are not compatible with Streets & Trips gps trail feature. If i remember correctly, there is code to keep this feature from attempting to work when the gps trail is active (maybe this prevention mechanism is not working correctly). I will confirm to you later, but i think that the gps trail is red and will keep these functions from working correctly. This is the same problem with any red icons you may insert on the map or any red POI category. The latest v2.55.2 beta has an extra function to help a little when other red items are on the map, but the actual algorithm for GPS icon search is simple to avoid taking too much time to detect the GPS (that could be moving)
Here an extract of S&T Keys 2009 about F6 function:
Quote:
Tips: When using this function, avoid using icons with a RED color. This will fool the GPS icon search logic and may keep it to find the GPS icon correctly (which is also RED). The GPS search logic can generally deal with a single red small icon, or single RED end point on the map, but not if there are more then one RED items. If you activated in S&T "find near by" categories with RED icons, you may get into problem if they are found on your map by the search logic. In this situation, the search logic may switch to a slowlier search technic trying to search a limited region in the center of the screen, to find the GPS icon.
For curiosity, did you try this feature with version 2.55.1 or 2.55.2?
Are you driving fullscreen navigation or not while using?
What kind of computer/os you have (with memory?)?
In a specific situation where you press the F6 key, was the GPS icon was stable on the screen?
Waveguide, how do you get Streets & Trips 2010 to produce a GPS trail in yellow?
SpadesFlush said:
Where did you get that the trail in Streets & Trips is yellow? The picture shown is with the trail imported in Arcview which shows it in yellow
Quote:
Waveguide, how do you get Streets & Trips 2010 to produce a GPS trail in yellow
Quote:
Originally Posted by MisterMoonlight
waveguide:
So if you have time before i test it myself, you can do some tests without using the gps trail to see if it improves things...
For curiosity, did you try this feature with version 2.55.1 or 2.55.2?
Are you driving fullscreen navigation or not while using?
What kind of computer/os you have (with memory?)?
In a specific situation where you press the F6 key, was the GPS icon was stable on the screen?
So if you have time before i test it myself, you can do some tests without using the gps trail to see if it improves things...
For curiosity, did you try this feature with version 2.55.1 or 2.55.2?
Are you driving fullscreen navigation or not while using?
What kind of computer/os you have (with memory?)?
In a specific situation where you press the F6 key, was the GPS icon was stable on the screen?
Thanks for the reply. I will test inserting the pushpin without GPS trail on and report back to you here. I'm hoping I can get both functions to work simultaneously, or at least be able to temporarily turn the GPS trail off while the car is stopped, insert the pushpin, then turn the trail back on and then continue to the next point.
The color of the GPS trail in Streets & Trips 2010 is blue, and I don't see any way to change that. The pushpin color was red, so even though there shouldn't be a color conflict I'll try changing the pushpin icon and see if it has any effect. I'm using the v2.55.2 beta, not using full screen navigation, the GPS task pane was open while I was driving, running Streets & Trips 2010 on a Dell Latitude E6500 laptop w/2.5 Ghz and 4Gb ram (3Gb usable since it's a 32-bit OS). There were a few instances where the GPS trail was on and the pushpin inserted relatively close to the correct position, maybe 40' was the best I got? I'll do some more experimenting and report back, I'm hoping I can get it to work together with the trail. Again, thanks so much for your help, it's very much appreciated.
Sorry, but when I view the image in his link http://home.comcast.net/~lindian2/Image1.jpg, I see a yellow line.
Spadesflush said:
Yep, but this is not Streets and Trips. Look at top left of the picture. It is ArcView software. It is just the way (in yellow) Arcview displays the imported data from S&T...
I think this is that software:
ArcView
Quote:
Sorry, but when I view the image in his link http://home.comcast.net/~lindian2/Image1.jpg, I see a yellow line.
I think this is that software:
ArcView
Waveguide said:
If the gps trail is blue, you should have no problem with it, but i am not sure the current v2.55.2 will accept to do it when the gps trail is active??
But your pushpin must not being red. Choose a yellow one and it should work. Like i explained, any red item on the map, icons, pushpins, nearby POI, etc, will interfere with the GPS icon search logic which is also red. The algorithm is able to discriminate 1 small additionnal red item on the map max, but it should not be located near the GPS icon, or it will cause problem...
Try it with yellow pushpin and with/without gps trail and give me your result. I didn't have time to drive with the 2010 version yet which is still a beta...
Quote:
The color of the GPS trail in Streets & Trips 2010 is blue, and I don't see any way to change that. The pushpin color was red, so even though there shouldn't be a color conflict I'll try changing the pushpin icon and see if it has any effect.
But your pushpin must not being red. Choose a yellow one and it should work. Like i explained, any red item on the map, icons, pushpins, nearby POI, etc, will interfere with the GPS icon search logic which is also red. The algorithm is able to discriminate 1 small additionnal red item on the map max, but it should not be located near the GPS icon, or it will cause problem...
Try it with yellow pushpin and with/without gps trail and give me your result. I didn't have time to drive with the 2010 version yet which is still a beta...
Waveguide:
After limited tests, i was able to use the gps trail S&T function with the F6/F10 functions. My assumption if it is not a red pushpin problems, you may also check in find nearby and deselect all categories that have red in their icons. Then if you still have problems, take a look at the performance of your system with the gps trail active.
In the past with old version of S&T, gps trail slow things down a lot especially if the trail is very long. Maybe the operation of S&T is quite slow in your situation. This could cause maybe problems with S&T keys which is quite timing based related. If S&T is becoming very slow, it is possible you may get different buggy situations?
When you make additionnal tests, just post your results if there are any bug related with this and a correction is desired in the 1st release. After that, new versions may come at a much slowlier rate
After limited tests, i was able to use the gps trail S&T function with the F6/F10 functions. My assumption if it is not a red pushpin problems, you may also check in find nearby and deselect all categories that have red in their icons. Then if you still have problems, take a look at the performance of your system with the gps trail active.
In the past with old version of S&T, gps trail slow things down a lot especially if the trail is very long. Maybe the operation of S&T is quite slow in your situation. This could cause maybe problems with S&T keys which is quite timing based related. If S&T is becoming very slow, it is possible you may get different buggy situations?
When you make additionnal tests, just post your results if there are any bug related with this and a correction is desired in the 1st release. After that, new versions may come at a much slowlier rate
Quote:
Originally Posted by MisterMoonlight
Waveguide:
After limited tests, i was able to use the gps trail S&T function with the F6/F10 functions. My assumption if it is not a red pushpin problems, you may also check in find nearby and deselect all categories that have red in their icons. Then if you still have problems, take a look at the performance of your system with the gps trail active.
In the past with old version of S&T, gps trail slow things down a lot especially if the trail is very long. Maybe the operation of S&T is quite slow in your situation. This could cause maybe problems with S&T keys which is quite timing based related. If S&T is becoming very slow, it is possible you may get different buggy situations?
When you make additionnal tests, just post your results if there are any bug related with this and a correction is desired in the 1st release. After that, new versions may come at a much slowlier rate
After limited tests, i was able to use the gps trail S&T function with the F6/F10 functions. My assumption if it is not a red pushpin problems, you may also check in find nearby and deselect all categories that have red in their icons. Then if you still have problems, take a look at the performance of your system with the gps trail active.
In the past with old version of S&T, gps trail slow things down a lot especially if the trail is very long. Maybe the operation of S&T is quite slow in your situation. This could cause maybe problems with S&T keys which is quite timing based related. If S&T is becoming very slow, it is possible you may get different buggy situations?
When you make additionnal tests, just post your results if there are any bug related with this and a correction is desired in the 1st release. After that, new versions may come at a much slowlier rate
Again, thanks very much for your work on this. I tried testing the F6/F10 functions again using YELLOW icons for the pushpins instead of red, and that seems to have resolved the problem.
When I inserted the pushpin at current location it was much more accurate - nearly on the trail, maybe about 10-20 feet off at most, which is tolerable for our needs. Also, the function seemed to work the same when the GPS trail was toggled on or off, so that's good news also - we'd prefer to keep the trail on and do the insert pushpin rather than remembering to shut it off and on each time. The way it's setup now seems to work just fine - I have no other issues. I will avoid using anything red from now on in the program, since that's definitely something that's prone to causing errors.
So, thanks again - your hard work on this is very much appreciated. -Dave
Waveguide said:
Don't forget if you have selected some categories in "find near by places", some of them have red icons and if they are activated, you will get some tiny red icons on the map even if you don't use the "find nearby" function. So if you want to improve F6/F10 functions, you may turn them off as well if unneeded...
Quote:
I will avoid using anything red from now on in the program, since that's definitely something that's prone to causing errors.