subsurface.git/map-widget/qml, branch v5.0.2

Revert "map: remove selectedDivesChanged"

2020-04-27T12:48:37Z

This reverts commit cd474996948b7592ab2973b7f936320a663a914e. The signal removed in the reverted commit was used in Subsurface-mobile. So removing it, caused a not running app. Signed-off-by: Jan Mulder

maps: disable link to Google maps on iOS and Android

2020-04-25T20:18:41Z

It appears that on those two platforms you now need a paid API key in order to have this feature work. Certainly not something I'm going to do. Signed-off-by: Dirk Hohndel

map: remove selectedDivesChanged

2020-04-25T20:05:31Z

The qml-widget seems to catch selectedDivesChanged signals of the MapWidgetHelper and reemit them. However, there seems to be nobody listening to this signal? Let's remove this for now to make debugging of the signals easier. Signed-off-by: Berthold Stoeger

maps: show the dive site when opening Google map

2020-04-20T01:52:15Z

I'm not sure if Google used to show the POI marker at the center location in the past or if this is actually a new feature. Either way this appears to do the right thing in my testing. Note that we need a 'plus' to connect the point of interest cooridnates, but a 'comma' to connect the map center coordinates. Reported-by: Chirana Gheorghita Eugeniu Theodor Signed-off-by: Dirk Hohndel

Map: export isSelected as attribute from MapLocationModel

2019-09-06T18:48:47Z

Recently we changed the MapLocationModel-items to store whether they are selected. Thus, we can directly export an isSelected flag instead of calling a function taking a dive-site argument. 1) This makes the QML easier to read. 2) This avoids passing pointers through QML which has caused us lots of pain. Signed-off-by: Berthold Stoeger

Map: calculate the z value in the model

2019-09-06T18:48:47Z

Since not fully reloading the map on selection change, the selected sites were not moved to the top. Not calculating the z-value in QML, but making it a simple model property helps. Signed-off-by: Berthold Stoeger

Desktop: show all selected dive sites on click

2019-09-06T18:48:47Z

When clicking a dive site on the map, the QML code would set the selected dive site, but then all dives of dive sites in the vicinity were set. But still only the clicked-on dive site was shown. Therefore, don't set the list of selected dive sites in QML, but later in DiveListView::selectDives(), where we know all the dives that were selected. This, again, gives nasty entanglement of diverse widgets and models. Signed-off-by: Berthold Stoeger

Map: generate pixmap name in model

2019-09-06T18:48:47Z

Experimentation has shown that the image of a flag will only be changed after dataChanged() if it is a simple property. The old code had a complex QML expression and then - for some reason - it didn't work. To give us better control over the flags and avoid full reloads of the map therefore introduce a model-property pixmap name. The name depends on whether the site is selected and if not, whether we are in divesite-edit mode. This makes the code rather convoluted. Firstly, we have to save whether the site is selected in the map-item. Secondly we have to access the global map-widget, which in turn has to go to the map-widget helper (layering violation!). Signed-off-by: Berthold Stoeger

Map: explicitly reload selected map on click

2019-09-06T18:48:47Z

When clicking on a flag 1) The QML would call MapLocationModel::setSelected() with fromClick = true 2) MapLocationModel::setSelected() would emit a signal selectedLocationChanged() 3) MapWidgetHelper would catch that signal and do the actual processing. Other functions would call MapLocationModel::setSelected() with fromClick = false, which would not emit the selectedLocationChanged() signal. Detangle this a bit by calling the selectedLocationChanged() function directly from QML and remove the fromClick parameter. Signed-off-by: Berthold Stoeger

Map: catch null divesites in map widget selection code

2019-08-28T14:12:01Z

Just to be sure, refuse to add null divesites to the selection. Moreover, refuse to call the setSelected function on a null-divesite. I got an unfriendly Qt-Warning there: "Passing incompatible arguments to C++ functions from JavaScript is dangerous and deprecated." "This will throw a JavaScript TypeError in future releases of Qt!" Signed-off-by: Berthold Stoeger