Re: [pmapper-users] Attribute search error - is this correct behaviour?

2008-10-30 Thread Dejan . Gambin
I agree with you Armin. I really don't need this necessarily. What I wanted - I have a point layer with 27.000 points labeled by a cadastrial number. When I try to turn on this layer at full extent, it freezes and never ends. So I put MAXSCALE for this layer and everything works ok. The layer

Re: [pmapper-users] Attribute search error - is this correct behaviour?

2008-10-30 Thread Armin Burger
You can try to modify this behaviour in toc.js. But if you use categories then you will have overlapping functions to enable/disable the checkbox and you need to figure out which logic you want, and then modify everything accordingly. armin On Thu, Oct 30, 2008 at 8:06 AM, [EMAIL PROTECTED]

Re: [pmapper-users] Attribute search error - is this correct behaviour?

2008-10-30 Thread Thomas Raffin
Hi, I often do that. For instance: I use the geographical objects in a table but with few attributes. This is the layer I have in the TOC. Then I use the same geographical table, but joined with attributes tables. Those are the queriable layers in my mapfile. So only 1 is shown, but the other

[pmapper-users] Attribute search error - is this correct behaviour?

2008-10-29 Thread Dejan . Gambin
Hi, I want to display a point layer (labeled by its attribute field) on the map, without showing it in TOC/legend. If I am correct, it can be done by setting the status of the layer to DEFAULT in map file and removing it from config.ini. Then it is drawn always. This works fine but doing

Re: [pmapper-users] Attribute search error - is this correct behaviour?

2008-10-29 Thread Armin Burger
Layers that are not in the config.ini will very likely not work with various functions like queries since they are not referenced in the p.mapper layer and groups objects (thats different objects than pure Mapscript layers). Hence they produce errors when trying to read some specific