| Versions |
  |
|
| Author |
 Topic  |
|
Ris
USA
679 Posts |
 Posted - 21 juil. 2005 : 21:07:45
|
quote:
Originally posted by lvgdgts
I haven't seen much for bugs being posted with this most recent beta. I know it's working great for me. I wanted to thank everyone at Mapopolis for their hard work and willingness to listen to the testers at this site. I liked Mapopolis before, but I like it much more now.
One question, though. Once this goes from beta to a general release, will it be the same, or will some features be left out? I ask because of the following post from Ris:
"We have yet to make a final decision about the focus of the enhancements for the next major version. One of the choices under consideration is routing".
I am assuming that he is talking about the next major version and not this release that has been in beta testing, but wanted to make sure.
Yes, I was talking about the next MAJOR version 5.x as opposed to the current beta testing of 4.5x. Features will not magically disappear before the final release of 4.5x. I hope 
The time is gone, the song is over, thought I'd something more to say. |
 |
|
|
lvgdgts
USA
30 Posts |
Posted - 21 juil. 2005 : 21:18:43
|
| Thanks Ris, that's what I thought. It may have come off as a dumb question, but I have seen things disappear from beta testing to major release before. It looks like this one is ready. |
|
|
|
AllanHvass
Denmark
396 Posts |
Posted - 22 juil. 2005 : 13:47:28
|
quote:
Originally posted by brobinson
Tried the proximity alerts on my way home and this is what I found. When I use a standard category (one that comes with a default installation), the Skip All function works until you have used it 4 times. After the fourth Skip All, the position no longer updates and the only way to recover is to exit Mapopolis and restart.
Dell Axim X50v, Motorola MPx220, Haicom 303E with bluetooth slipper
Tried 5 continuous "Ignore All" presses on POI alerts yesterday, without any problem. It must be a specific combinations with something else that is causing it.
I did however notice, as a few others have said, that POI alerts don't fire immediately. Usually, I've set alerts to 500m radius, and in that case it seems to happen fairly close to that. But yesterday going 130km/h on the highway and having set the radius to 1000m, I didn't get alerts before within 700m distance, or about 7-8 seconds too "late". I was wondering whether this is somehow related to some mph / km translation behind the scenes? 700m is fairly close to ½ mile?
Best regards
Allan Hvass
Using SmartPhone QTek 8020, 512MB miniSD, BlueTooth enabled Holux GM-210, Mapopolis, Parrot BT car kit |
|
|
|
jarredduq
USA
27 Posts |
Posted - 22 juil. 2005 : 18:07:27
|
With version 4.57, I've been having issues with the Backlight not staying on, even when set to "Backlight always on." The problem occurs approximately 5 out of 10 times I run the software. I'm using an Audiovox SMT5600 smartphone.
Thanks,
Jarred |
|
|
|
Ris
USA
679 Posts |
Posted - 22 juil. 2005 : 21:25:35
|
quote:
Originally posted by AllanHvass
quote:
Originally posted by brobinson
Tried the proximity alerts on my way home and this is what I found. When I use a standard category (one that comes with a default installation), the Skip All function works until you have used it 4 times. After the fourth Skip All, the position no longer updates and the only way to recover is to exit Mapopolis and restart.
Dell Axim X50v, Motorola MPx220, Haicom 303E with bluetooth slipper
Tried 5 continuous "Ignore All" presses on POI alerts yesterday, without any problem. It must be a specific combinations with something else that is causing it.
I did however notice, as a few others have said, that POI alerts don't fire immediately. Usually, I've set alerts to 500m radius, and in that case it seems to happen fairly close to that. But yesterday going 130km/h on the highway and having set the radius to 1000m, I didn't get alerts before within 700m distance, or about 7-8 seconds too "late". I was wondering whether this is somehow related to some mph / km translation behind the scenes? 700m is fairly close to ½ mile?
Best regards
Allan Hvass
Using SmartPhone QTek 8020, 512MB miniSD, BlueTooth enabled Holux GM-210, Mapopolis, Parrot BT car kit
I am also not able to reproduce or find any potential code problems with Skip All.
If you ask for proximity alerts at 1000m distance, but don't get an alert until 700m, then we consider that not to be working correctly. 7-8 seconds is a MUCH bigger delay than I would ever expect. We have made several changes to the proximity alerts underlying functionality which should make it more responsive.
The time is gone, the song is over, thought I'd something more to say. |
|
|
|
Ris
USA
679 Posts |
Posted - 22 juil. 2005 : 21:48:03
|
4.58 is NOT yet done or available, HOWEVER, I am posting the tentative release notes as a sanity check. Have we overlooked anything?
VERSION 4.58
* Adds complete open/selected map file list to saved route information, reopens all listed maps when recalling the route
* Improves responsiveness of proximity alerts at high speed with small search radius
* Fixes Text to Speech handling of the abbrevations BR, ST, and DR
* Fixes combo box sizes on Find Address screen
* Fixes bug with popup menus and GPS map updates
* Rolls back the Turn Reminder Pane to bold text under the small format, as in 4.56
Smartphone Only
* Fixes vertically truncated text on status box
* Fixes Refresh button on Sound Settings screen
* Fixes vertical scroll bug in all settings screens when wrapping "down" from the bottom instantly to the top
* New layout for General Program Options mostly fixes remaining vertical scroll problems
* Shifts the contents of the Proximity Alerts Settings dialog 5 pixels to the left
The time is gone, the song is over, thought I'd something more to say. |
|
|
|
Dr_StrangeTrick
United Kingdom
379 Posts |
Posted - 22 juil. 2005 : 22:11:32
|
Hi Ris, it looks good to me.
With respect to the proximity alerts I also suffer from the same problem when I use the warning box (not very often) and on most occasions I can reproduce the variable timing issues with the proximity alert.
However I have been testing this on and off for some time and no matter what speed I approach the POI if I maintain a constant speed then the countdown is practically spot on. Its only when I change speed (safety camera's) that the countdown becomes miles out.
I don't want to delay the release any further but I think that the countdown needs to be dynamic and recalculate possibly every second that way no matter how much you change your speed you should only be one second out.
Orange C550, TomTom BT GPS |
Edited by - Dr_StrangeTrick on 22 juil. 2005 22:12:32 |
|
|
|
AllanHvass
Denmark
396 Posts |
Posted - 22 juil. 2005 : 23:02:00
|
quote:
Originally posted by Dr_StrangeTrick
I don't want to delay the release any further but I think that the countdown needs to be dynamic and recalculate possibly every second that way no matter how much you change your speed you should only be one second out.
I also don't want to delay release any further, so if we don't hit the right timing of POI alerts on this version, so be it. I do however think, that if it's not too hard, then POI alert range should not be based on distance but on time, just like the turn reminders. In the city, getting alerted 500m before arriving at something can still be 2 min. to get there, whereas 500m on the highway is 15 seconds or less, practically not enough time to slow down before the speed camera, eh I mean rest place...
Best regards
Allan Hvass
Using SmartPhone QTek 8020, 512MB miniSD, BlueTooth enabled Holux GM-210, Mapopolis, Parrot BT car kit |
|
|
|
Ris
USA
679 Posts |
Posted - 23 juil. 2005 : 00:24:41
|
quote:
Originally posted by Dr_StrangeTrick
Hi Ris, it looks good to me.
With respect to the proximity alerts I also suffer from the same problem when I use the warning box (not very often) and on most occasions I can reproduce the variable timing issues with the proximity alert.
However I have been testing this on and off for some time and no matter what speed I approach the POI if I maintain a constant speed then the countdown is practically spot on. Its only when I change speed (safety camera's) that the countdown becomes miles out.
I don't want to delay the release any further but I think that the countdown needs to be dynamic and recalculate possibly every second that way no matter how much you change your speed you should only be one second out.
Orange C550, TomTom BT GPS
Try it when you are not moving. "Closing in 15" is short for "closing this message box in 15 seconds". It is NOT meant to be interpreted as "closing in on, and arriving at, this POI in 10 seconds" It is NOT an ETA. It is not meant to give the impression that it is an ETA. It is a fixed 15 second timer. Is there a way that we can make this distinction clearer?
The time is gone, the song is over, thought I'd something more to say. |
|
|
|
Ris
USA
679 Posts |
Posted - 23 juil. 2005 : 00:33:58
|
quote:
Originally posted by AllanHvass
quote:
Originally posted by Dr_StrangeTrick
I don't want to delay the release any further but I think that the countdown needs to be dynamic and recalculate possibly every second that way no matter how much you change your speed you should only be one second out.
I also don't want to delay release any further, so if we don't hit the right timing of POI alerts on this version, so be it. I do however think, that if it's not too hard, then POI alert range should not be based on distance but on time, just like the turn reminders. In the city, getting alerted 500m before arriving at something can still be 2 min. to get there, whereas 500m on the highway is 15 seconds or less, practically not enough time to slow down before the speed camera, eh I mean rest place...
Best regards
Allan Hvass
Using SmartPhone QTek 8020, 512MB miniSD, BlueTooth enabled Holux GM-210, Mapopolis, Parrot BT car kit
That's a good suggestion, but will take some careful consideration. Please note that our proximity alerts do not know whether you will actually arrive at the alerted POI, nor do we care. The alerted POI might be on another street, or might even be 90 degrees to your right, having only just barely brushed through your search bubble.
The time is gone, the song is over, thought I'd something more to say. |
|
|
|
Ris
USA
679 Posts |
Posted - 23 juil. 2005 : 00:37:26
|
quote:
Originally posted by jarredduq
With version 4.57, I've been having issues with the Backlight not staying on, even when set to "Backlight always on." The problem occurs approximately 5 out of 10 times I run the software. I'm using an Audiovox SMT5600 smartphone.
Thanks,
Jarred
It sounds like the operating system on your device is overly aggressive about saving power and ignores application requests to keep the backlight on. This is quite common and there is unfortunately nothing more that we can do about that problem at this time.
The time is gone, the song is over, thought I'd something more to say. |
|
|
|
Ris
USA
679 Posts |
Posted - 23 juil. 2005 : 02:05:51
|
I have reproduced the problem with GPS updates stopping after skipping all proximity alerts. It appears to occur completely randomly, and will also happen on a Pocket PC, so it is not restricted to the phone. We're working on it.
The time is gone, the song is over, thought I'd something more to say. |
|
|
|
Ris
USA
679 Posts |
Posted - 23 juil. 2005 : 03:49:36
|
Regarding the problem where the GPS stops updating and cannot be stopped or restarted following Skip All proximity alerts, here are our findings... The GPS thread becomes frozen due to an error while purging the sound queue if you press Skip All while the proximity alert voice prompt is still in progress. You should only be able to reproduce the problem by pressing Skip All while Mapopolis is still talking. If you disable the voice prompt option with proximity alerts, or if you wait for it to finish talking before pressing Skip All, you should NOT be able to reproduce the problem. If you press Skip All while Mapopolis is still reciting the name of the POI (or within a second or two of when it finishes) then it should ALWAYS cause the GPS to stop updating in 4.57. We have corrected this problem for the upcoming 4.58 release.
This may be the same or a very similar cause of the other GPS-stops-updating problem that occurs intermittently when shutting off power to the pocket PC, so we have also added some error recovery code specifically designed to counteract lost critical section locks in order to force them to be released after a timeout of 10 seconds, only for the GPS thread.
The time is gone, the song is over, thought I'd something more to say. |
|
|
|
Dr_StrangeTrick
United Kingdom
379 Posts |
Posted - 23 juil. 2005 : 07:53:22
|
quote:
Closing in 15" is short for "closing this message box in 15 seconds
Ah ha that explains it, it looks like almost everyone assumed this meant the time to reach the POI 
In that case I would suggest the button on the warning box be changed "OK" and underneath or alongside have "XX seconds" maybe with a countdown bar similar to a Windows auto close prompt 
Orange C550, TomTom BT GPS |
|
|
|
jarredduq
USA
27 Posts |
Posted - 23 juil. 2005 : 19:19:33
|
quote:
Originally posted by Ris
quote:
Originally posted by jarredduq
With version 4.57, I've been having issues with the Backlight not staying on, even when set to "Backlight always on." The problem occurs approximately 5 out of 10 times I run the software. I'm using an Audiovox SMT5600 smartphone.
Thanks,
Jarred
It sounds like the operating system on your device is overly aggressive about saving power and ignores application requests to keep the backlight on. This is quite common and there is unfortunately nothing more that we can do about that problem at this time.
The time is gone, the song is over, thought I'd something more to say.
The thing is, in versions prior to 4.57 this was not a problem.
Thanks,
Jarred |
|
|
|
Topic |
|
|
|
| This page was generated in 3,85 seconds. |
 |
|
- 
- 
4.6 Pre6 - 2 September 2005
Forum Locked
