Hello, 

since kiozen asked me not to "produce too much noise" in the QMapShack
issue list, I dare to continue discussion on this list. Is this OK?

I encountered a rare but still possible way to crash QMapShack

https://bitbucket.org/maproom/qmapshack/issues/140/qmapshack-crashes-speicherzugriffsfehler#comment-28547334

The issue is solved but will take quite some time to trickle down the
update flow of all distros etc. And beyond this issue, other nasty
thinks may lurk in the plethora of murphy's laws, like power shortage
and bluescreening operating systems (got one last night ;-\\ ) .

I see an aggrevated risk of data loss due to the two step storing
approach when working with QMS: When you edit some item (track, route,
waypoint), you enter a "change-finish" workflow that "feels like" saving
your work. But as I understand - at least when your data is in a gpx
project - this is not the case: Your data is not saved to disk until you
save the gpx. And in a database, I see the "synchronize" function. So I
assume the same problem in general.

Am I correct ? Or Is there any way to restore work not yet finally
saved - maybe not yet documented ;-) ? Are there any plans to implement
this in the foreseeable future? I know such things from firefox or from
open office. I can imagine that this is quite a bunch of work which
may not find an easy way to the top of programmers priority list.

Meanwhile, maybe some warning lines in the manual could reduce user
annoyance. May I offer to produce a page like "backup your work" in the
wiki, to be included in the manual ? 

Or would it suffice co include proper warnings here

https://bitbucket.org/maproom/qmapshack/wiki/DocHandleGpxFiles
https://bitbucket.org/maproom/qmapshack/wiki/DocGisItemsEditMultiple



-- 
Wolfgang Rosner


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users

Reply via email to