Rob Norris [Sun, 26 Aug 2012 13:18:10 +0000 (14:18 +0100)]
Add zoom by bounds capability when using the zoom tool and holding the SHIFT key and left click to select the zoom in area.
Similar to zooming in on the OpenStreetMap default map.
In the zoom tool mode, when the SHIFT key is held down and then left mouse button is pressed it draws a bounding box area on the display.
When the left mouse button is released the zoom is performed on the selected area.
Rob Norris [Thu, 2 Aug 2012 01:09:04 +0000 (02:09 +0100)]
More intuitive zoom actions involving the mouse to retain the location under the pointer within the viewport bounds.
As per request SF#3547438, which is clearly much better behaviour - since clearly this is the point of interest the user wants to see and thus subsequent zoom requests keep focusing on that area without having to recenter the display.
The modifiers of CTRL+SHIFT and mouse zoom retain keeping the center point in the center (which is in fact a reversal of the previous setting - unlikely to effect many users, as I didn't even know of this feature myself).
Note the keyboard & menu zoom requests always maintain the center point.
Rob Norris [Tue, 4 Sep 2012 22:37:20 +0000 (23:37 +0100)]
Prevent crashing when attempting to import with GPSBabel a file and not specifying the file type (due to a malformed (null) result of the GPSBabel file types list).
Rob Norris [Wed, 13 Jun 2012 19:48:28 +0000 (20:48 +0100)]
Rework Track Draw by Velocity into Draw by Speed with a simple traffic light colouring scheme.
Determine the colour of the trackpoint (and/or trackline) relative to the average speed
* . slow points are red
* . average is yellow
* . fast points are green
An option is provided to control the percentage factor away from the average speed to determine the transistions to the differing colours.
This now removes the previous Draw by Velocity mode options, which was unclear how it worked and unlikely any one actively uses it.
Thus this means the .vik file format has changed slightly but other than generating warnings all other features will still work.
Rob Norris [Wed, 2 May 2012 23:06:04 +0000 (00:06 +0100)]
Geotagging: add option to overwrite existing waypoints.
This is especially useful when after the first attempt, the waypoints were generated are in the wrong position and you want to repeat the tagging process but with a different time offset. Such as having daylight saving time issues (e.g. GMT v BST)
Rob Norris [Mon, 16 Jul 2012 22:11:16 +0000 (23:11 +0100)]
Remove create_realtime_trackpoint call in cleanup which can crash.
Crashes in g_list_last on my system, although I don't understand why.
However what is the point of creating another trackpoint when stopping, especially since the track is immediately deleted!?
Hence the call has been removed.
Rob Norris [Wed, 9 May 2012 16:25:14 +0000 (17:25 +0100)]
Make the track name a property of the track.
This is important step in being able to support undo operations.
This also gives the ability to have multiple same named tracks.
ATM maintain usage of a hash table for the list of tracks, but instead of using the (forced unique) name for the hash,
use a simple integer as a kind of UUID.
Rob Norris [Mon, 16 Apr 2012 17:31:51 +0000 (18:31 +0100)]
Make the waypoint name a property of the waypoint.
This is important step in being able to support undo operations.
This also gives the ability to have multiple same named waypoints.
ATM maintain usage of a hash table for the list of waypoints, but instead of using the (forced unique) name for the hash,
use a simple integer as a kind of UUID.
Evan Battaglia [Thu, 10 May 2012 19:41:04 +0000 (21:41 +0200)]
Add CalTopo 7.5" (24k) USGS Topos!
msrmaps is going away, add these just in time!
I contacted them about using their tiles. I'm a bit unclear on the license (if there is one?), because it isn't displayed on their home page, but what I mentioned what I wanted to do with them (use them to make my own custom topos for free redistribution) he said that was OK:
"Because the underlying data is public domain I don't know if I could actually prevent someone from reassembling the tiles into a map, but I wouldn't want to even if I could. By all means feel free to do what you're describing."
When I asked about using the tiles in Viking, he basically said go ahead: "You guys should go ahead and use the tiles, and if bandwidth becomes a concern we can sort it out then."
Many extensions can be added through a simple configuration file.
Currently, only user's home directory is used to load such configuration.
This patch add support for some standard locations in system.
The behavior can be affected by XDG_DATA_HOME and XDG_DATA_DIRS standard
environment variables.
Viking uses g_debug function. But in glib 2.32, the g_debug behavior changed and all
DEBUG messages are discarded, unless G_MESSAGES_DEBUG is set. So, "viking -d"
no more work as its design was to mute DEBUG messages when "-d" is not set.
Now, printing is restored via a dedicated function.
Rob Norris [Sat, 11 Feb 2012 19:31:46 +0000 (19:31 +0000)]
Fix Track Properties graph blob marker drawn at wrong elevation when elevation graphs have different min/max heights.
Use separate values for each elevation graph minimum values and indexing.
Normally these values are the same but sometimes they differ due to differing methods of altitude array creation.
Rob Norris [Sat, 4 Feb 2012 11:36:46 +0000 (11:36 +0000)]
Example script that can be used to upload a track as a route to a predefined GPS device.
This can be used inconjunction with the export GPX with external program to upload a route to the GPS in absence of true GPX route support in Viking at present.
Rob Norris [Fri, 20 Jan 2012 01:00:50 +0000 (01:00 +0000)]
Add function to return an average moving speed for a track.
This method doesn't use samples that differ over the specified time limit - effectively skipping that time chunk from the total time - hence removing the 'stationary' bits to give only the moving parts.
Rob Norris [Fri, 20 Jan 2012 00:27:28 +0000 (00:27 +0000)]
Add ability to open a TrackWaypoint layer with an external program (default JOSM).
This is ideal for editing around the track and waypoints with OSM, as it's very unlikely Viking will ever be an OSM editor - it's best left to other dedicated programs.
The layer is converted to a temporary GPX file, but it is not deleted as loading it with another program is not instantaneous.
For now it is up to the user to delete it / use system temp cleanup methods.
The program can be changed by the user and is stored in the preferences.
This *hasn't* been tested on Windows OSs. It's possible a full path to the program may be needed to invoke it on such systems.