![]() Just before today’s update I confirmed that that Bluetooth was listed by Gnome as still Off. So would it be possible to never let your recalculation "extend over" gaps? Even if you edit 1,2 and 3, points 2 and 3 are effectively end and start points of a section and should therefore keep their timestamps.I have had this regularly following updates to Fedora 36 (and perhaps earlier with 35) then it goes away again after a further update. The exact result of course depends on the actual location, but we might get something like 12:00:00 - 12:05:00 - 12:10:00. ![]() So assume we have the following points:Ĭurrently, if you move points 1 and 2, the time difference between 2 and 3 will also be smoothed. But I think you wil agree that gaps are there to separate different sections of a track. Now my request concerns gaps: Currently, that recalculation also takes place across gaps. So there's a slightly hidden possibility to edit without touching the timestamps. In principle a useful feature, but I always disagreed with Menion about existing points (and I would still like to see a switch "Auto-Recalculate On/Off" in the track editor).Īnyway, we found a (kinda hidden) compromise: When only moving a single point, Locus will not touch its timestamp. Now when moving existing points, Locus will also recalculate the timestamp based on the new distances. For adding trackpoints, it's obvious that a new time has to be calculated. Menion, you might remembered some years ago we discussed about the "timestamp-recalculate" feature of the Track Editor?! For those who don't know: In the Track Editor ("Modify Track"), when using "Insert/Edit trackpoint", moving track points will also change their timestamps. One little improvement for the Track Editor:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |