Such a line can be constructed with:
<rule e="way" k="*" v="cliff">
<line stroke="#777777" stroke-width="0.3" stroke-linecap="butt"/>
<lineSymbol src="file:/symbols/richtungspfeil-klippe.png" align-center="false" repeat="true"/>
</rule>
The problem: Currently it's not possible to define the gap between two symbols.
Question: Is it possible to control the gap with an additional parameter? <rule e="way" k="*" v="cliff">
<line stroke="#777777" stroke-width="0.3" stroke-linecap="butt"/>
<lineSymbol src="file:/symbols/richtungspfeil-klippe.png" align-center="false" repeat="true" repeat-gap="0dp"/>
</rule>
Cheers Klaus
PS: Screenshot (from user jusc) created with Locus Pro which has such a feature.
--
You received this message because you are subscribed to the Google Groups "mapsforge-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapsforge-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapsforge-dev/9d7bff98-fb43-4943-953c-2c2a9dc15671%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I have added something like this to rescue-exp, new attributes aredy: offset to center of linerepeat-gap: gap between repeatsrepeat-start: distance from start to first symbol
--
You received this message because you are subscribed to the Google Groups "mapsforge-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapsforge-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapsforge-dev/8f7d0659-cde2-4357-a20c-d1d142c45eae%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mapsforge-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapsforge-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapsforge-dev/6590da91-7c3f-4ffd-8f71-3cbe4ae0ba62%40googlegroups.com.
Concerning tests I have to wait for a new cruiser beta / atlas beta version with support for this feature.
My suggestion for the future is to think about moving away from dy with fixed values, even if they are scaled.
I prefer the logic we have at symbols with positions relative to the element and the engine puts them at the right adjacent places.
--
You received this message because you are subscribed to the Google Groups "mapsforge-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapsforge-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapsforge-dev/54D283B1.7020207%40gmail.com.
Tobias can you open an issue about that in GitHub issues in order to not forget it?
My suggestion for the future is to think about moving away from dy with fixed values, even if they are scaled.
I prefer the logic we have at symbols with positions relative to the element and the engine puts them at the right adjacent places.
Another thing I hoped to use dy for is to put a border to natural reserves, without the nasty tile border effect we got with MF 0.4. It actually mostly works at higher zoom levels, but screws up spectacularly at ZL13 and below. Test theme attached, try on any forest area.
--
You received this message because you are subscribed to the Google Groups "mapsforge-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapsforge-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapsforge-dev/54D3DEE0.2060301%40gmail.com.
The one thing I am just thinking about as I pushed the change is that this change will apply universally, i.e. if someone already has a different rendertheme with dy values depending on zoomlevel this will still scale those lines further. Is this an issue? I would prefer to keep the change to the library as small as possible, but an option would be to increase the version number of the rendertheme and apply the scaling conditionally on the rendertheme version number. (So we would move to rendertheme V5 and put all other rendertheme changes into this until we come to mapsforge 0.6 when rendertheme V5 would then officially be released.)
Let me know. I am not using dy much myself at the moment, so this affects me little.
--
You received this message because you are subscribed to the Google Groups "mapsforge-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapsforge-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapsforge-dev/54D760B0.4010504%40gmail.com.
--
You received this message because you are subscribed to the Google Groups "mapsforge-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapsforge-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapsforge-dev/54D8C24A.7050001%40gmail.com.
Ok, let's just wait for feedback on the second commit and then just push the stuff to master, and make a 0.5.1rc1.
Having finally escaped the European winter, I feel like moving at a faster pace again.
On 09/02/2015 04:26 μμ, Ludwig wrote:
Ok, let's just wait for feedback on the second commit and then just push the stuff to master, and make a 0.5.1rc1.
Sorry for not publishing yet Beta versions of Cruiser / Atlas bundle based on dev for people to test the latest changes..