Messages

[Menion]

Hello Menion.

I've just find out that the GPS notification, that I had always set to beep when GPS lock, dont't works anymore.

I've tryed to set up again in GPS, Global, enable notification and setup a beep notification when GPS lock but whatever I setup, when I click OK Lucus say: "Notification not set!". Strange behaviour, isn.'t it? The version is 2.5.1.

By the way I would like to suggest to add a third button in the GPS window where already are "My Location" and "Bussola" buttons, that can enable or disable the external Bluetooth GPS receiver.

I very soon swich between external GPS (much more precise and power saving) and internal (comfortable and always available). Should be nice to can swtitch between them, if you like.

Conbgrats for all the recent updates, very useful about the new zooming behaviour. ;-)

See you.

I've installed the test version and everything seems works well for me

[Menion]

Hello Menion.

First of all a little preliminary statement: when a new version is released, I appreciate a lot many of the new feature, even if I am not used to send greetings for that all the time. On the other hand, when I find some "defects", I am very punctual to report. That doesn't mean that I do not appreciate all the hour of your work, or I exact the solution. I like just to mention what I find it at least "strange", in order to let you know. That's it.

After that, I find some strange zoom and finger-moving map behavior.

I make a little list to try to be precise.

1. Moving map with finger has some defects (compared with previous releases). By the way, I use a single-core 1ghz CPU on a 480 x 854 pixels and I've ever had amazing performances with Locus. The defects is that: when moving the map with finger, after releasing the finger the map continue moving but not simultaneously: the screen divides vertically in two parts (1/3 on the left, and 2/3 on the right) and they moves at 2 different speed (one part in late), until the movement is finally finished. This is not professional-like, annoying after a while, and in any case Locus has never done it! It happen with any kind of raster maps (both RMaps SQL that TAR). The effect is more visible moving diagonally the map, but also clearly visible vertically and horizontally. I do not need or exact the maximum smoothness and fluidity, but the splitting in two part and one it's rendered in late until all it's full stopped is annoying, especially if I have to explore a map and move it often or continuously.

Tell me if I am explaining properly, or if you prefer I can record a video and send you by eMail.

2. The zooming feature that now supports automatic-lock zoom and go over and below 100% (so 50% and 200-800%) should really be excludable (seems there's no way now). It was very comfortable, before, to can safety zoom just and only inside the REAL resolution of the map, reaching in a fast way the maximum and the minimum real resolution avoiding to go over.. Now I always go under and over the real resolution.

In any case, the 50% zooming with TAR maps gives buggy results: always and continuous disappearing of part of the map. Moving in a way, some part disappear, other appear. And so on in any direction.

My suggestion, here, just for TAR maps (because they are non unlimited area like the on-line maps), is to create a button to fast switch between the current zoom and the smallest available zoom-ratio. ;-)

___________________________________

In any case thanks a lot for all the other improvement. Locus seems the most wonderful mapping software. Better then many avionics moving maps! I have some suggestion for the future (avio and car usage ;-) ..

[Menion]

Oh thanks a lot, Menion.

All this thread bugs solved on last v.2.4.3 :-D

All my congrats!

[Menion]

perfect, thanks. Interesting issue. I have no idea why this error happen, but I did some testing before place where it happen, so it should be fine in next version. Anyway it's not answer why you see only one attached point when you import first file.

May you please wait till next release and check this import in next version? I did some small improvements so it should work fine in next version. If not, we'll fix it next time .. thanks

I have absolutely any urgent needs, Menion ;-) Any!

I was writing down this issue just to help.

I can easily solve importing tracks and way-points in separate GPX files.

I just try to give notice if I find something strange. That's it.

In any case thank you very much for your professional character, competence, and kindness also.

[gynta]

2 Small...:
after import (after i stoped endless importloop) is see:
 5 points 2tracks (MTB Rome small track + MTB Rome small track filtered) and can tap on all poitns
if i try to delete this 5 POIs in the data manager - Locus crash - deleteting the whole categorie fix this

1 Small...:
after import (after i stoped endless importloop) is see:
 5 WP (red dots) 1track (MTB Rome small track filtered) and can tap on all wp

I do not know whether OziExplorer Version 3955n - http://www.oziexplorer.com produces this problem or Locus..

Hello gynta

It's very strange, but we can confirm that we have different reactions.

for me:
1 Small: import procedure works (any endless problem) but it confirms to have imported 1 track (correct) and no mention of way-points (while they're 5). After that the track is visible, and only the last WP is visible as red point (named: SPEED). And if I tap it, Locus do an "unsuspected termination".

2 Small: import procedure works (any endless problem) and it confirms to have imported 2 tracks (correct) and 5 way-points (correct). And after the import everything seems working perfectly.

[Menion]

Hello Menion.

I've sent you the MIUI crash report. Let me know if you prefer a complete debug log strings.

In any case I use Locus Pro licensed v.2.4.2 and this is my system:

Build: MIUI-2.4.20
Bootloader: 0x0000
Kernel: Linux version 2.6.32.9-gb08c3c8 (vfcj78@zch68lnxdroid50) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Fri Jun 3 11:40:33 CST 2011

Board: jordan
Brand: MOTO
Build ID: MIUI-2.4.20
Build type: user
Codename: REL
Device: umts_jordan
Incremental version: 2.4.20
Model: MB525
Network name: I WIND
Network type: 3
Phone type: 1
Product: MB525_RTGB
Release: 2.3.7
Time: 7/6/2012 10:27
UI language: it_IT

[20120607_000233.jpg]

So I've attached some screen shots.

The first, 20120607_000233.jpg, show the gpx with 1 track and 5 waypoints. Unfortunately just the last of the 5 waypoints is visible. The ather 4 are missing. And if I click the only waypoint (called SPEED) Locus crash.

The second, 20120607_000310.jpg, show the gpx with 2 tracks (one over the other, but they're two!) and the 5 waypoints. All correct.

I can attach also the log of the crash if you want.

I've tryed also with other maps and track + waypoints. Always happend when I have just 1 track with some waypoints...

I see 3 tracks. I can load all 3 tracks without any problem. But only the last track in the list shows 5 red dots (waypoints).

Jusc, 3 tracks??
The file MTB Rome 1 Small Track with wps.gpx (20120607_000233.jpg) have exactly 1 tracks + 5 waypoints. And doesn't work properly;
The file MTB Rome 2 Small Track with wps.gpx (20120607_000310.jpg) have exactly 2 tracks + 5 waypoints. And it works properly.

[track]

Just to notice that the import procedure of a single GPX containing 1 (and just one) track + waypoints seems fails.
GPX files containing 2 or more tracks + waypoints seems work perfectly.

I have attached a zip file:

- MTB Rome 1 Small Track with wps.gpx: doesn't work properly: Locus imports just the track and the last waypoint. And selecting it produce a crash.
- MTB Rome 2 Small Track with wps.gpx: it works.

The GPX are generated by OzExpl 3955n and they seems correct.

That's it.

At disposal for test.

[Menion]

Hello Menion.

I don't want to bother you, and I promise I'll silently (  :oops:  ) wait for the day, if so, you will give more support on TAR.

Maybe the developer of mapc2mapc will write to you to allineate the goal of a full zoom support on TAR. Should be nice ah!

About the efficientness I have, on the ather hand, to say that: what you mean with "efficient"?
Space file compression level?
Programming efficientness?

If the second, OK. I have no skill to know, and I completely trust in you.  

If the first, I have to say something.  :roll:
Images intensivly optimized and palette compressend into modern PNG are not-more-compressible.They're alreay as their best.
So avoiding any kind of scaling for the full zoom level (the biggest) mans: raw quality and raw space.  

Quality does matter  8-)  No way ...

Any kind of force-scaling of the full zoom level (like SQLite need) means considerably loss quality and quite a lot more space. And a much more processing resources, also!  

Camparison on maps format space and quality just confirm this easly.

In any case I vote for that, and I did all my best to go in deep in this quality topic.

My enforce ends here. So I'll just at disposal for tests, and no more words on it  :lol:

See you :-)

[mapc2mapc]

Hello Menion.

Some news for you ;-)

I have written to the mapc2mapc developer in order to know more about ful raw 100% zooming in SQLite format and how things works in TAR format.

Here is the topic: //http://mapc2mapc.freeforums.org/process-png-to-sqlite-without-stretch-rotate-raw-100-zoom-t38.html

So we will have TAR support, and maybe also with zooming, over TAR MAP.

Seems is not possible avoid forcing image resample in SQLite format.

In TAR, instead, YES! :-)

Hope you will revalue TAR format.

At disposal for map testing. :-)

See you.

[ozfx to locus.zip]

Hello Menion. And really congrats for this amazing software!

I write here just to let you know that I am one of the person who appreciate ozfx to locus.zip.

Offcourse MAPC2MAPCNET is much more advanced, but there are some maps who still prefer the old java cutter.

MAPC2MAPCNET, infact recreate all the images, while imageCutter.jar not! Some graphocal images are well seen after the treatment of MAPC2MAPCNET, but the lossless 100% zoom scale is completely missing.

All maps are subjet to rezooming. Ex:
Map scale is 2,53 metres/pixel : zoom level 15 is 3,51 metres/pixel
Map scale is 3,17 metres/pixel : zoom level 15 is 3,51 metres/pixel

Rescaling images are NEVER lossless. I am a grapher, so I work a lot on raster map before reach the best results. Is a pitty to loose a lot o quality and zoon forcing an image to reach the RMap/sqlite fixed zoom levels.

Is much better to work on adjusting the projectum zoom, instead rendering images to reach fixed projectum. 12,13,14,15,16 and so on.

My map with "scale 3,17 metres/pixel : zoom level 15 is 3,51 metres/pixel" is awful after MAPC2MAPCNET stripping, especially because is not a picture but a graphical png low bit color, high density sharp image.

imageCutter.jar is perfect for this, and the image is just super sharp and detailed on old tar format, but seems Locus doesn't support datum Roma1940. Isn't it?

I have a 9000x6000 png of just 4.2MB with datum Roma1940. (I can send you to let you know).

It would be nice to finally have a simple but powerful and up-to-date imageCutter.jar for the graphical png images.
And yes, the MAPC2MAPCNET is very very good for creating photographic high quality zoom levels (as and better than img2ozf do) but, also there, I really do not undertans why to force the souce image always! And why avoiding pure 100%.

It's a sqlite limit? So this could be the why a lot of users miss OZI format and Androzic, even if this software is good but not as complete as yours.

I know Locus is particulary made for on-line sources. But your software is really too god to not be able to work with custom raster personally georeferenced images at a real 100 of quality.

Finally just to let you know that I dont miss ozfx3 file format (just miss a software to do tha same for sqlite at loslessy 100% zoom level). But a map lover as me need to find a way to have all his wonderful PNG, or GeoTIFF images viewed at full quality and dimension on your just amazing Locus.