|
2019-03-26
, 21:59
|
|
Community Council |
Posts: 1,669 |
Thanked: 10,225 times |
Joined on Nov 2014
@ Lower Rhine
|
#642
|
The Following 4 Users Say Thank You to mosen For This Useful Post: | ||
|
2019-03-27
, 06:20
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#643
|
>5000km done
Try satellite maps as worstcase.
It is not a major issue. Just the idea of indicating accuracy was brought up and i made the connection to the uncertainty circle as low hanging fruit to achieve that without altering the position marker.
I am often thinking about how to improve the route display and if i have something ready to explain i will most likely mix above idea in those drafts.
The Following 4 Users Say Thank You to rinigus For This Useful Post: | ||
|
2019-03-27
, 06:57
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#644
|
The Following 3 Users Say Thank You to rinigus For This Useful Post: | ||
|
2019-03-27
, 09:28
|
|
Posts: 764 |
Thanked: 2,888 times |
Joined on Jun 2014
|
#645
|
For translators to Czech: please review your translation and restore english names for all variables - strings enclosed in {}. For example, translate
"In {distance}, {direction}"
to
"V {distance}, {direction}"
currently its translated to "V {vzdálenost}, {směr}" which will make Pure Maps rather unhappy.
hoping that translators are @TMO
The Following 3 Users Say Thank You to nthn For This Useful Post: | ||
|
2019-03-27
, 12:41
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#646
|
I think you should be able to work around this issue by only referencing those untranslatable variables with a '%s' or '%0' type string that refers to the variable elsewhere in the code, that way they won't accidentally get translated. Of course, you then need to add translator notes to every such string explaining which variable does what, but I think it'd be an improvement.
The Following 5 Users Say Thank You to rinigus For This Useful Post: | ||
|
2019-03-27
, 17:08
|
|
Community Council |
Posts: 1,669 |
Thanked: 10,225 times |
Joined on Nov 2014
@ Lower Rhine
|
#647
|
The Following 5 Users Say Thank You to mosen For This Useful Post: | ||
|
2019-03-27
, 17:37
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#648
|
The Following 4 Users Say Thank You to rinigus For This Useful Post: | ||
|
2019-03-27
, 17:45
|
|
Community Council |
Posts: 1,669 |
Thanked: 10,225 times |
Joined on Nov 2014
@ Lower Rhine
|
#649
|
@mosen, thank you very much! These are of great help! I would vote for + sign option for consistency, otherwise SFOS variant is good as well
The Following 3 Users Say Thank You to mosen For This Useful Post: | ||
|
2019-03-27
, 18:03
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#650
|
The Following 4 Users Say Thank You to rinigus For This Useful Post: | ||
Re suspend/resume media player: so, that means it player specific, isn't it? Which is rather poor design in my mind and should be solved on OS level (mixing players?). I guess we can do as others are, just implement it in platform-specific code.
Re blabbing/sleeping preference: the main risk is draining the battery of users who don't use this feature. I'd be cautious and add it under preferences.
Re closing PM and not being able to start: we had this issue earlier and never managed to track it down. is it on J1? No clue when was it discussed in this thread. Try to check if sailfish-qml is still running from prev invocation. I can look it up how to do that, but I'd prefer to continue with some other stuff. Maybe you can figure out the solution with ps and kill...
Re position marker without fix: its provided by OS and Pure Maps does not check anything so far regarding GPS status. Only things we get are position, uncertainty, speed. Direction, is probably calculated, but I don't remember correctly. Whole QtLocation idea was that the code is independent of positioning source. If we want to track how many satellites we have and data like this, specific backend has to be written. Must say, not high in my priorities at the moment.
Re circle under location marker. I am sure it was discussed and then concluded (or pushed by me) that we just improve the contrast of the marker (which we did by reducing opacity). In practice, I see marker well now, way better than before. Let's see if I say the same after driving for decent amount of hours.