The Following User Says Thank You to dwaradzyn For This Useful Post: | ||
![]() |
2011-11-09
, 17:02
|
Posts: 11 |
Thanked: 5 times |
Joined on Aug 2010
@ RO
|
#382
|
Thanks for your report. This shows that value of tilex and tiley can go way out of range due to some bug. If you are able to reproduce this issue it would be very helpful to put some info about it here. Currently I have no idea how to reproduce this.
Because this is not the first time I see a user with this issue and the reason for this bug still remains unknown I will simply remove the bug outcome in next release. I will limit those values to valid range during config file load so next time it will be enough to restart the app after this bug occurs.
The Following User Says Thank You to _invisible_ For This Useful Post: | ||
![]() |
2011-11-13
, 23:17
|
Posts: 317 |
Thanked: 787 times |
Joined on Oct 2009
@ Krakow, Poland
|
#383
|
The Following 4 Users Say Thank You to dwaradzyn For This Useful Post: | ||
![]() |
2011-11-14
, 09:27
|
Posts: 638 |
Thanked: 1,692 times |
Joined on Aug 2009
|
#384
|
The Following User Says Thank You to xes For This Useful Post: | ||
![]() |
2011-11-16
, 08:15
|
Posts: 40 |
Thanked: 61 times |
Joined on Jan 2011
|
#385
|
The Following User Says Thank You to Keferen For This Useful Post: | ||
![]() |
2011-11-16
, 18:32
|
Posts: 317 |
Thanked: 787 times |
Joined on Oct 2009
@ Krakow, Poland
|
#386
|
wow the N9 version looks epic. but i think there needs to be a way to change 2D/3D on the map view without having to go to settings. mayne ot can replace the zoom slider as cloudgpsN9 version has pinch zoom and rotate ?
![]() |
2011-11-18
, 13:37
|
Posts: 638 |
Thanked: 1,692 times |
Joined on Aug 2009
|
#387
|
![]() |
2011-11-18
, 22:21
|
Posts: 317 |
Thanked: 787 times |
Joined on Oct 2009
@ Krakow, Poland
|
#389
|
...impatience is a bad disease..... but curiosity maybe worse!!
Any news for the N900's lovers?
![]() |
2011-11-20
, 14:56
|
Posts: 317 |
Thanked: 787 times |
Joined on Oct 2009
@ Krakow, Poland
|
#390
|
{ "layouts":[ { "name":"English", "abbreviation":"EN", "lowercaseChars":[ "qwertyuiop", "asdfghjkl", "zxcvbnm", ", ." ], "uppercaseChars":[ "QWERTYUIOP", "ASDFGHJKL", "ZXCVBNM", ", ." ], "alternateLowercaseChars":[ "~@#123_%()", "&$456+:;\"", "!7890/?", "- '" ], "alternateUppercaseChars":[ "~@#123_%()", "&$456+:;\"", "!7890/?", "- '" ] }, { "name":"Polish", "abbreviation":"PL", "lowercaseChars":[ "qwertyuiop", "asdfghjkl", "zxcvbnm", ", ." ], "uppercaseChars":[ "QWERTYUIOP", "ASDFGHJKL", "ZXCVBNM", ", ." ], "alternateLowercaseChars":[ " ę ó ", "ąś ł", "żźć ń ", "- '" ], "alternateUppercaseChars":[ " Ę Ó ", "ĄŚ Ł", "ŻŹĆ Ń ", "- '" ] } ] }
Because this is not the first time I see a user with this issue and the reason for this bug still remains unknown I will simply remove the bug outcome in next release. I will limit those values to valid range during config file load so next time it will be enough to restart the app after this bug occurs.