[mkgmap-dev] Changes to require name defined in the style file

Fri Mar 28 10:03:10 GMT 2014

Hi 
The style sheets are rather a black art to me.  To get a name on a waterfall do I need to use
natural=waterfall	{name '${name}'}	[0x6508 resolution 20]
or
natural=waterfall	name=* {name '${name}'}	[0x6508 resolution 20]
Neither appear to be working?  I have upgraded to R3132.
As for the generic question on warning users on major style sheet changes.  The idea sounds great but implementation not so much.  By that I can not figure out a sensible way to do it.  Warnings after a while get ignored so prefer warnings than means why something did not work rather than suggestions of improvements.
While it was great that mkgmap had a lot of inbuilt corrective and often guessed what the user wanted the downside was the style sheets became rather mysterious with hard to figure out the logic for newbies.  At least with the current approach they are less "magical" but does mean some update work as people tend to be weeded to "their" style and typ sheets.  
We are gradually developing a mkgmap community but it forms into three broad groups.  Mad mappers, map cutters using mkgmap, and people that simply want an img.  The map cutters are the rarest group and we short of reverse engineer solutions or "steal" them from each other.
Cheers Brett
From: gpetermann_muenchen at hotmail.comTo: mkgmap-dev at lists.mkgmap.org.uk
Date: Fri, 28 Mar 2014 10:34:33 +0100
Subject: Re: [mkgmap-dev] Changes to require name defined in the style file

Hi Brett,

you are not the 1st and probably not the last to be trapped. 
I thought about a check that warns the user but I found nothing that works always.

Any ideas out there?
How can mkgmap detect that the user has to modify the style to get a usable result?

Gerd 

From: brussell237 at live.com.au
To: mkgmap-dev at lists.mkgmap.org.uk
Date: Fri, 28 Mar 2014 20:26:49 +1100
Subject: Re: [mkgmap-dev] Changes to require name defined in the style file

Hi Gerd
The perfect answer! 
I understand the improved logic of the changes, and yes it makes sense, but a side effect is some work is now required editing the style sheet.  No great hassle as at least I was not going mad.
Cheers Brett
From: gpetermann_muenchen at hotmail.com
To: mkgmap-dev at lists.mkgmap.org.uk
Date: Fri, 28 Mar 2014 10:21:17 +0100
Subject: Re: [mkgmap-dev] Changes to require name defined in the style file

Hi Brett,

please look at
http://www.mkgmap.org.uk/news/2013/12/22/more-flexibility-in-style-files-style

Doesn't that answer your questions?

Gerd

From: brussell237 at live.com.au
To: mkgmap-dev at lists.mkgmap.org.uk
Date: Fri, 28 Mar 2014 20:16:23 +1100
Subject: [mkgmap-dev] Changes to require name defined in the style file

Hi All
Trouble been a bit slow to update or more likely just plain with my styles but I think that somewhere along the line the automatic use of the name changed.  I find I now need to add 
& name=*{name '${name}'}
to any point of interest to display the name.  In the past I think I only needed name=*
No great problem as I can re-work my style sheet but for my own sanity check did this extra vigour in defining the style creep in?
Cheers
Brett 		 	   		  

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev 		 	   		  

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev 		 	   		  

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev 		 	   		  

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140328/08c628fc/attachment.html>