errr, I must say I have no idea why this happens, there is no logical reason
for such behaviour.
if I may ask, why did you extend the query plugin when you can simply use
the tableRules registry functions ?
there is an example in the Cartoweb3 tutorial
http://cartoweb.org/stats/click.php?id=43 step 9
the table rules functions are explained there
http://www.cartoweb.org/doc_head/docbook/xhtml/dev.newplugin.html#dev.newplugin.special.tables
this way you dont have to touch the coreplugin to add a new column to the
query result
regards
Oliver
Hi all,
again me :-) Now, I want to group some of my layers using the
layers.ini. The other layers should be displayed ungrouped. Therefore, I
define a root LayerGroup with the following children:
1) the group of some layers
2) all the other layers, which should not be grouped
It looks very nice like I wished, BUT
Before doing this, I extended the query coreplugin. I did it according
to the CartoWeb documentation. In my extension, this plugin adds a new
column to the table containing some values taken out of an Access db. If
I use the query plugin WITHOUT having the root LayerGroup, everything
works fine (db request will be executed). If I use the plugin WITH the
root LayerGroup, CartoWeb seems to use the original query plugin, since
there my column is missing and there are no error messages. Additionally
I cannot identify any problems in the cartoclient.log.
Is there an explanation for this behaviour?
Thanks in Advance
Carolin
--
Carolin Latze
Research Assistant
Department of Computer Science
Boulevard de Pérolles 90
CH-1700 Fribourg
phone: +41 26 300 83 30
_______________________________________________
Cartoweb-users mailing list
[email protected]
http://lists.maptools.org/mailman/listinfo/cartoweb-users
_______________________________________________
Cartoweb-users mailing list
[email protected]
http://lists.maptools.org/mailman/listinfo/cartoweb-users
