Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Tobias

Pages: [1] 2 3 ... 7
1
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: Yesterday at 09:10:02 »


I must correct, I used Elements theme. It displays a lot, but when zooming out town names should have the right prio...

Please use Elevate for normal or densely mapped areas. Elements is meant for countries like Iceland, northern Scandinavia etc.

2
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 23, 2019, 22:55:09 »
Newest Elevate and a v4 map, and the city name overshadowed by "Wohnwagen-Platz"... Sizes of town/city names like totally random.
Could you post a screenshot?

3
Of course, this theme is only for V3 maps.

Please could you update your theme to V4 maps?
I really love it and used it always with the LoMaps.
The original Tiramis├╣ 3 should work with V4 maps, just put it in a seperate directory in the theme folder. You find it in the link in the first post.

4
Themes - Vector maps / Re: mapsforge v4 themes for Openandromaps
« on: April 28, 2019, 21:02:59 »
Is there a definitive guide to the usage of these tags anywhere?
The best thing is still this:
https://github.com/mapsforge/mapsforge/blob/master/docs/Rendertheme.md
That's a reason why I made the table, to have at least a complete overview. Of course one can add a lot to it, but it's a start.

5
Themes - Vector maps / Re: mapsforge v4 themes for Openandromaps
« on: April 28, 2019, 10:19:27 »
I made a reference which mapsforge version support which tags that can be found here:
https://www.openandromaps.org/oam-forums/topic/mapsforge-rendertheme-reference

6
Thanks for the hint about the problem tags in the theme for V4 on your site.
I made a reference which mapsforge version support which tags that can be found here:
https://www.openandromaps.org/oam-forums/topic/mapsforge-rendertheme-reference

7
Themes - Vector maps / Re: [Theme] TOTM
« on: April 21, 2019, 09:17:39 »
Refused is probably the wrong word; I don't think that the mapsforge developers ever got a pull request for those Locus extended theme rules that was refused. That would also be the easiest solution, if a mapsforge rendertheme V6 supports those tags, it would be much easier to adjust the themes. But someone has to write the pull request ;-)
In the meantime there's still things that are improved via the mapsforge community, one of last big issues is now gone - curved pathText is now working:
https://github.com/mapsforge/mapsforge/pull/1112

8
Discussion/New features / Re: Update of map core (2019)
« on: April 20, 2019, 15:13:47 »
Perfect :).
It is now finally possible to have two or more XML files in the same subdirectory and all these files appear for selection. It is then easy to share the same icons for themes without messing the root "_themes" directory as was necessary till now.
That's great to hear, can't wait for the release with all those improvements. Seems like I'll have a one theme file fits all apps solution. Some theme cleaning/deinstallation option is also a good idea.

9
Discussion/New features / Re: Update of map core (2019)
« on: April 19, 2019, 22:13:58 »
Yes, should be. Because I see no other clear suggestion here. Except the suggestion from Tobias here

So only the proposal above (using a renderer according to theme version, when V3 maps are used) would work properly.

which is too complicated to create (as I wrote before).
Themes optimized for V3 maps does not work correctly in new system when tiles are scaled in new MapsForge renderer and oposite.
I'm fine with that, at least there's finally full V4-theme compatibility that is correctly rendered (with V4-maps), this is way more important than full backwards compatibility, which would be just the icing on the cake.

10
Discussion/New features / Re: Update of map core (2019)
« on: April 12, 2019, 21:15:50 »
As I wrote above backward compatibilty of the render engine is great, so you can throw any theme or map version at 0.11 (except locus extended), old V1 themes will also be scaled according to dpi etc.

But there's no "forward" compatibilty, so it makes no sense using a render engine 0.3 (locus ext.) with maps higher than V3 and themes higher than V1 (whatever happened to V2 and V3?).

So only the proposal above (using a renderer according to theme version, when V3 maps are used) would work properly.

11
Discussion/New features / Re: Update of map core (2019)
« on: April 12, 2019, 20:36:41 »
I also just checked the new version, the rendering of V3 maps with V4 themes is wrong.
What renderer is used for V3 maps with V4+ themes? If it's the forked 0.3 version (locus-extended) it makes not a lot of sense, as at least mapsforge 0.5+ is needed.
I would propose checking the theme version in the xml-file, if it's version="1" and/or locus-extended="1", use the Locus-Fork, if it's version="4" or higher, use the standard engine.

12
Discussion/New features / Re: Update of map core (2019)
« on: April 07, 2019, 19:34:08 »
I don't fully agree with Tobias and really don't understand the zooming idea.
For example, when I change from LoMap (or OAM V3) ZL 20 @ 75% to OAM Mapsforge V4 the zoom changes to ZL 18 @ 100% with the map showing the same area.
I meant that the rendering is finally how it's meant to be for mapsforge maps, so no rendering differences anymore for the major apps. I think it depends on user preferences if switching maps should show the same area or the same zoom level (although most without deeper understanding will prefer probably the former).
That obviously seriously affects what items are displayed at what map size. Will I need to change all the zoom-min settings in the V4 theme or what?
Until now with fixed tile size in order to have the map look the same on any device one would need a different theme for every major ppi step. You adjusted your theme to look fine with the ppi of your device, but it looked different on one with a different ppi screen.
You may have to adjust the V4 theme now, but it will look alright and show the same things in the same area no matter if you use it on a 160ppi tablet or 480ppi smartphone.

PS - @John: I also had my issues with this when it was introduced in standard mapsforge, but after a while I realized this is a pretty genius idea. Once set it works flawless.

13
Discussion/New features / Re: Update of map core (2019)
« on: April 07, 2019, 18:48:40 »
"zoom level/magnificaction can't be switched on when touching the map scale" - may you describe it little?
In the map view the map scale (e.g. 200 m) in the lower left corner can't be switched to show the zoom level/magnification in brackets by touching it (V4 OAM) any more.
Quote
"scale of V4 maps" - not same, hmm it's possible, but the difference should be really small
My mistake, as I didn't have the magnification in the map scale, I didn't realize that the map was slightly zoomed. Now I switched the top bar to show map info, and with 100% in all apps the view is the same - perfect!

14
Discussion/New features / Re: Update of map core (2019)
« on: April 07, 2019, 08:44:41 »


Are you using an OpenAndroMap V4?
http://download.mapsforge.org/maps/v4/
Italy.map
And
Slovenja.map
Those maps don't contain contour lines. Only OpenAndroMaps contain all the data Elevate needs to work properly.

15
Discussion/New features / Re: Update of map core (2019)
« on: April 06, 2019, 19:32:00 »
No way, Elevate Hiking or City, flagged and unflagged contour lines no results.
I also used your suggested procedure using top left back button.
It's the same with elements theme.
I tried to switch from italian to english language to test if it was something related to, but nothing
Are you using an OpenAndroMap V4?

Pages: [1] 2 3 ... 7