AlpineQuest & OfflineMaps

Hi again! Proximity alerts are working well, thank you! But I ran into a problem if a lot of alerts (I made 240 notifications), they are very inconvenient to remove the one on the card.
I offer 2 options:
1. Snap Proximity alerts to point to as the point - Proximity alerts are also deleted and not left on the map.
2. Or, make a folder for Proximity alerts, so they can be saved, hide, show, and delete ... especially the "Delete all" (screenshot)

Hi,

Right now it's not possible to save proximity alerts like waypoints and other items.

However:
- You can create a group of proximity alerts: you need to create alerts from a waypoints set instead of creating single alerts;
- In the next update, when you have more than 5 single proximity alerts, they will be displayed as a group in the "Displayed placemarks" list.

I understood, thanks!

And you can make not 5 Proximity alerts, but a controlled value? For example, starting from 2, through the option in "user_settings.conf"

Yes it will be of course
A new beta should be available tomorrow.

Thanks! Sincerely thank you!

Hi again,
I've published beta version 2.2.5.r6252. I've made various technical changes so it may be more unstable.
With this version you can use this user setting to group the alerts from 2: (I know the "1" is not very logical, I'll change in the next update so the value to enter is "2")

Hello again!

So, I have to test a version of the R6252

1.
I checked otsiyu "landmarks.proximity.group_display_nb", like all works ... but:
- If "landmarks.proximity.group_display_nb = 1" is not spelled out in the "user_settings.conf", that option does not work (it is not used at all by default, right?)
- if = 1, is valid for 2 Proximity alerts; if = if 2, 3 is valid for Proximity alerts .... etc. (And probably intended was greater than the value of 1, but just in case, said a screenshot)




2. If you create Proximity alerts without waypoints via menu "Create a placemark", they do not appear in the menu "Displayed placemarks".
However, if you create a waypoint, and attach it to the Proximity alert, then displayed and hidden Proximity alerts without waypoints. (screenshot)




3. It seems the menu "+ Custom item" do not have enough points (buttons) "Proximity alert" (screenshot)




4. More remarked on the R6252 version, I have become great in the thickness of the tracks, waypoints, icons, and title tags. I think the size of lost or ignored in the setting "user_settings.conf": landmarks.painter.paths_factor; landmarks.painter.icons_factor; landmarks.painter.labels_factor. Perhaps even some options are ignored.

5. I really liked the option "landmarks.proximity.group_display_nb", can do the same, only for waypoints? folder to the right of the point is displayed, if you have created more than 2 points? (screenshot)




If you notice any more bugs - be sure to write!
I hope to help you... Best regards!

6. When you create the first warning of the approximation, the program asks for access to the GPS and tries to include "GPS position" switch (it is noted in older versions have forgotten to say it, I do not know this is a bug or a feature )

In addition to paragraph 4, I noticed a bug... If you increase the value of "landmarks.painter.points_factor" option, the track thickness also increases (as if I uvelival value "landmarks.painter.paths_factor" option)

Hi,
I'll soon publish a new beta version. I've made various changes.
1: Improved: so the number is more logical.
2: Corrected.
3: I've added the proximity alert custom button.
4. Corrected (currently there is a problem with the user settings you're right).
5. Unfortunately it's not as easy, it would require some work so right now it's not possible. And as discussed I'm not even sure it make sense. A single waypoint is single. I think you should simply create set of waypoints.
6. This is the wanted behavior. It was like this in previous version. Because proximity alerts are only working if you turn on the GPS location.

Understood.
Thanks for work!

PS: What other changes will be in the next beta?

I've published a new beta version.
I have also included this request: viewtopic.php?p=12573#p12573
I'll make a complete release note when the version is officially released.

Thanks!
I updated to version 240, everything seems to work fine. Very good! Thank you so much!!!
If the bug is not, then the version of the 240 will be the final version 2.2.5?

Yes, I'll test it in beta for a few days and if everything is fine it will be released for everyone.