- 02 Aug, 2022 1 commit
-
-
Allows to filter the button number early.
-
- 01 Aug, 2022 1 commit
-
-
Corentin Noël authored
Handle double click on the primary button to zoom-in.
-
- 29 Jul, 2022 1 commit
-
-
James Westman authored
-
- 26 Apr, 2022 5 commits
-
-
James Westman authored
-
James Westman authored
Add shumate_map_zoom_{in|out} methods, which zoom the map in or out with an animation. Also use animation when zooming via scroll wheel.
-
James Westman authored
-
James Westman authored
-
James Westman authored
-
- 23 Apr, 2022 1 commit
-
-
James Westman authored
-
- 14 Apr, 2022 1 commit
-
-
Corentin Noël authored
Document the basics of each classes.
-
- 26 Jan, 2022 1 commit
-
-
Corentin Noël authored
It is not really required these days.
-
- 13 Jan, 2022 1 commit
-
-
This reverts commit ec655268.
-
- 01 Nov, 2021 1 commit
-
-
Removed the {append|prepend|remove}_map_source methods from ShumateLicense and replaced them with a `map` property. The license monitors changes to the map layers through a new `layers-changed` signal and updates the license text automatically. This also required adding `license` and `license-uri` properties to ShumateLayer. Currently only ShumateMapLayer implements them and they are taken from the map source.
-
- 14 Oct, 2021 2 commits
-
-
James Westman authored
-
The viewport was accidentally initialized twice, leaking the first one.
-
- 06 Oct, 2021 1 commit
-
-
Niels De Graef authored
The whole `SECTION` block is a gtk-doc specific annotation. Just immediately document the class/struct/interface with the usual docs syntax and gi-docgen will know what to do with it. There's also no worrying about exposed structs, since there are none in libshumate, and even if there were, you would still have to document them in the GIR. Finally, use proper linking as specified by the gi-docgen tutorial.
-
- 08 Sep, 2021 1 commit
-
-
Corentin Noël authored
It has been replaced by project-wide compiler flag.
-
- 26 Aug, 2021 1 commit
-
-
James Westman authored
The formula for calculating zoom between integer levels was incorrect--it was linear, rather than exponential like the overall function. This change makes zooming smoother and more consistent. Also, added shumate_map_source_get_tile_size_at_zoom to reduce code duplication.
-
- 28 Jul, 2021 1 commit
-
-
James Westman authored
Add support for rotating the map using touchscreen/trackpad gestures. This involved changing the gesture tracking code to support zooming and rotating at the same time. Also, some of the viewport methods had to be changed since the calculations now depend on both coordinates.
-
- 06 Jul, 2021 1 commit
-
-
Makes it clearer that it is the widgets that shoes a map.
-
- 30 Jun, 2021 1 commit
-
-
James Westman authored
They have been replaced by map layers and don't do anything anymore.
-
- 18 Jun, 2021 1 commit
-
-
Corentin Noël authored
ShumateMapSourceDesc is now gone as it wasn't providing any value. The ShumateMapSourceRegistry is now a GListModel implementation.
-
- 18 May, 2021 1 commit
-
-
James Westman authored
-
- 17 May, 2021 1 commit
-
-
Using the new continuous zoom feature, implement pinch to zoom gesture. Tested on both a trackpad and a touchscreen. Fixes #5.
-
- 06 May, 2021 1 commit
-
-
James Westman authored
The map layer now accepts fractional zoom levels by scaling the entire map layer with gtk_snapshot_scale().
-
- 06 Apr, 2021 1 commit
-
-
James Westman authored
Errors are now handled using GError and shumate_map_source_fill_tile_finish().
-
- 10 Mar, 2021 1 commit
-
-
This makes it easier to add layers in the correct order.
-
- 09 Mar, 2021 4 commits
-
-
Georges Basile Stavracas Neto authored
The check for the scroll deltas is reversed, correct that. It's worth noticing that we don't have to care about natural scroll, the values are reversed when it's enabled. Also make sure to not zoom out when dy is zero. Fixes: #4
-
Georges Basile Stavracas Neto authored
It doesn't seem to be useful enough to justify its existance, so just remove it. Adapt the Vala demo to not use it too.
-
Georges Basile Stavracas Neto authored
It currently is stub, and it doesn't seem to be much useful either. Remove the 'deceleration' property.
-
Georges Basile Stavracas Neto authored
Implement kinetic scrolling through a GtkGestureSwipe that is triggered after ending a drag. When triggered, it adds a tick callback to the view, and each tick calculates the new distance from the point where the drag end happened. The kinetic scrolling heuristic is copied and modified from GTK4. The deceleration rate is hardcoded for now, because the 'deceleration' property is stub, but that'll be fixed by the next commits. Fixes: #7
-
- 05 Mar, 2021 9 commits
-
-
Georges Basile Stavracas Neto authored
The same code is shared between the drag-update and drag-end handlers. We'll need this for kinetic scrolling, and in any case it's always good to share code.
-
Georges Basile Stavracas Neto authored
It certainly is never bigger than the maximum longitude!
-
Georges Basile Stavracas Neto authored
It is semi-officially deprecated. Also sneak in a small cleanup using g_clear_pointer().
-
Georges Basile Stavracas Neto authored
Remove function prototype that are not needed anymore.
-
Georges Basile Stavracas Neto authored
Instead of checking SHUMATE_IS_VIEW(view) twice in a row, do it only once in the public function, and add sanity checks for the coordinates too.
-
Georges Basile Stavracas Neto authored
'duration' by itself isn't descriptive to the time unit is uses, rename it to 'duration_ms' to make it clear it's in milliseconds.
-
Georges Basile Stavracas Neto authored
Move shumate_view_go_to_with_duration() to up in the file.
-
Georges Basile Stavracas Neto authored
It's slightly faster to use the signal id, and the detail quark, compared to the string variant (which has to decompose the string, acquire a global lock to find the signal id, etc.)
-
Georges Basile Stavracas Neto authored
For now, it uses a hardcoded ease-in-out-quad easing function, which was the default in the past. To use tick callbacks, we have to track the start (µs), and the duration (ms, converted to µs). The progress is calculated by checking the current frame time (µs). Easing is then applied to the progress itself, which is then used in a simple LERP operation to get the next latitude/longitude. Fixes #10
-