Re: [Viking-devel] Viking 1.5 Released
Robert Norris rw_nor...@hotmail.com writes: In order to support Relative Filenames (within primarily Viking files) and to (re)opening from where one last opened a file, Viking changes it's working directory to the last successfully opened directory. At first glance this sounds broken. In the specific use case above, this can be worked around using pwd to ensure a full path filename is used e.g.: viking gpx.viking `pwd`/ETREX30-archive/2013-10-01\ * That's a very unusual user interface. I have never seen another command-line program that took multiple filenames where each filename was interpreted relative to the previous directory. See commit SF#3028797: Remember last directory used when saving / opening main files. for when this was introduced: https://sourceforge.net/p/viking/code/ci/317298355967f8465d2ddff8ae61b428a188778f Perhaps to the best way is mitigate this issue is to only change the directory only when opening a .vik file type. Perhaps the previous-directory behavior should be strictly limited to the cases where it is documented to do that. I wonder if there is prior art in other programs, and if some token in filenames should mean relative to the .vik file. But I can see how all filenames that don't start with / in a .vik file should perhaps be relative to the .vik. pgpszeiFC6C1w.pgp Description: PGP signature -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Viking 1.5 Released
From: g...@ir.bbn.com Robert Norris rw_nor...@hotmail.com writes: In order to support Relative Filenames (within primarily Viking files) and to (re)opening from where one last opened a file, Viking changes it's working directory to the last successfully opened directory. At first glance this sounds broken. Yes, in fact it is. In the specific use case above, this can be worked around using pwd to ensure a full path filename is used e.g.: viking gpx.viking `pwd`/ETREX30-archive/2013-10-01\ * That's a very unusual user interface. I have never seen another command-line program that took multiple filenames where each filename was interpreted relative to the previous directory. This is just a workaround for this specific Viking 1.5 release. See commit SF#3028797: Remember last directory used when saving / opening main files. for when this was introduced: https://sourceforge.net/p/viking/code/ci/317298355967f8465d2ddff8ae61b428a188778f Perhaps to the best way is mitigate this issue is to only change the directory only when opening a .vik file type. Perhaps the previous-directory behavior should be strictly limited to the cases where it is documented to do that. I wonder if there is prior art in other programs, and if some token in filenames should mean relative to the .vik file. But I can see how all filenames that don't start with / in a .vik file should perhaps be relative to the .vik. After some thought, I think I was conflating two issues - such that the change directory answer, works only in limited cases. In the code, the use of GTK function gtk_file_chooser_set_current_folder() on opening files via the GUI, should address the SourceForge issue above - the change directory is I think unnecessary for this. Then to support relative paths, change to the directory when opening a .vik file but then simply return to the previous working directory (which it does not do ATM) so there no unintentional side effects. Thank you for taking time to report this issue. I will incorporate this fix in v1.5.1 with some other small fixes. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Viking 1.5 Released
Robert Norris rw_nor...@hotmail.com writes: After some thought, I think I was conflating two issues - such that the change directory answer, works only in limited cases. In the code, the use of GTK function gtk_file_chooser_set_current_folder() on opening files via the GUI, should address the SourceForge issue above - the change directory is I think unnecessary for this. Then to support relative paths, change to the directory when opening a .vik file but then simply return to the previous working directory (which it does not do ATM) so there no unintentional side effects. Thank you for taking time to report this issue. I will incorporate this fix in v1.5.1 with some other small fixes. Thanks - that approach sounds good to me. Separately, though, I think there may be a files-with-spaces bug, because I got different behavior renaming them to a.gpx and b.gpx. But I could have been confused and changed too many things when trying to check this. I'll recheck with 1.5.1 and update pkgsrc then. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Viking 1.5 Released
I have prepared but not committed a pkgsrc update for 1.5. However, I am seeing some odd behavior (on a mac, that I think I also saw on NetBSD). I tend to do viking gpx.viking ETREX30-archive/2013-10-01\ * to display all the tracks from a given (UTC of course :-) day. Under 1.4.2, this works fine, despite the horrific spaces. With 1.5, I get a The file you requested could not be opened. popup, apparently one for all but the first file. In order to support Relative Filenames (within primarily Viking files) and to (re)opening from where one last opened a file, Viking changes it's working directory to the last successfully opened directory. The easiest way to show it not working is like this: viking dir/file1.gpx file2.gpx After opening the first file the working directory is changed to 'dir'. Now it will attempt to open 'file2.gpx', but since this it is now in directory 'dir' it won't find file2.gpx as that is now relatively back in ../ In the specific use case above, this can be worked around using pwd to ensure a full path filename is used e.g.: viking gpx.viking `pwd`/ETREX30-archive/2013-10-01\ * See commit SF#3028797: Remember last directory used when saving / opening main files. for when this was introduced: https://sourceforge.net/p/viking/code/ci/317298355967f8465d2ddff8ae61b428a188778f Perhaps to the best way is mitigate this issue is to only change the directory only when opening a .vik file type. Be Seeing You - Rob. If at first you don't succeed, then skydiving isn't for you. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Viking 1.5 Released
Viking 1.5 released 2013-10-13 = Download = My PPAs for Ubuntu have now been updated here: http://launchpad.net/~rw-norris/+archive/viking Also note that a general forum has been enabled on the SourceForge website: http://sourceforge.net/p/viking/discussion/ Although it is intended more for those who don't use emailing lists. -- Be Seeing You - Rob. If at first you don't succeed, then skydiving isn't for you. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
[Viking-devel] Viking 1.5 Released
Viking 1.5 released 2013-10-13 = Download = http://sourceforge.net/projects/viking/files Source code and Windows 32bit Installer Release. = What is it? = Viking is a free/open source program to manage GPS data. You can import and plot tracks, routes and waypoints, show OSM maps under it, add coordinate lines, make new tracks and waypoints, hide different things, etc. You can visit the project web site: http://viking.sourceforge.net/ = What's New? = == Many New features since [[Version-1.4.2]] == * Startup preferences for ease of use. * Multi layer/track statistics. * Multi layer/track or waypoint detailed lists. * Control sorting of layers and quick show/hide all options. * Configurable layer defaults. * Optimizations when loading and drawing large numbers of tracks. * Allow higher zoom levels up to 1/32 (OSM z22 equivalent but maps only requested up to z19). * Retain internal options across sessions. * Selectable online router service provider (now including OSRM) * 'Via' points online route refining. * Download a file directly from an URL. * Datasource acquiring files from URLs related to the current view. * Support timestamps (read only) in waypoints. * Support naming trackpoints. * Request downloading a region of maps over multiple zoom levels. * Support Compressed My OSM Traces files (requires libbz2 and libmagic). * Support opening files drag and drop on to the viewport. * Support relative paths in Viking files. * Add support for OSM Humanitarian (HOT) Style Map. * Advanced preferences. * Optional track labelling on the viewport. * Translations for the Basque language. * Improved Help Manual. * Many internal improvements. == Fixes since 1.4.2 == * Fix crashing if attempting to Extend a Route via the Route Finder when the route has no points. = Contributors = * Rob Norris * Guilhem Bonnefille * Greg Troxel * Sven Eckelmann = Translations = * Ján Neščivera sk.po: created * alexgabi eu.po: created * lann fr.po: updated * Alexander ru.po: updated * Radek Stastny cs.po: updated * Cristian Marchi it.po: updated * Tim Schulz de.po: updated * Xuacu Saturio ast.po: updated * Mantas Kriaučiūnas lt.po: updated = Distributors / Building from Source Notes = New dependencies on libraries libbz2 and libmagic are enabled in the build by default. The extra source Debian package dependencies are libbz2-dev and libmagic-dev -- Be Seeing You - Rob. If at first you don't succeed, then skydiving isn't for you. -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134071iu=/4140/ostg.clktrk ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
