Letractively / morisoliver

Automatically exported from code.google.com/p/morisoliver
0 stars 0 forks source link

Orange symbology is showing for editable layers #63

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I pulled down the latest code and set this up: 

        toolSettings.editTool.layers = [
                {
                        featureType: "AFREEMAN.GEOSERVER_TEST_LINE",
                        layerTitle : "Geoserver Editable Line", // must match whatever is found in folderset for this layer.
                        split: true,
                        snapTo: ["AFREEMAN.GEOSERVER_TEST_LINE","GISDATA.TOWNS_POLY"]
                }
        ];

I'm going to snap AFREEMAN.GEOSERVER_TEST_LINE to itself or GISDATA.TOWNS_POLY.

When I fire up OLIVER I see these 2 layers drawn in orange underneath any other 
layers that I draw.
Now, I should probably draw the two layers anyway, so I do (GISDATA.TOWNS_POLY 
in black outline, and AFREEMAN.GEOSERVER_TEST_LINE in red).
The AFREEMAN.GEOSERVER_TEST_LINE in red covers the orange, but the 
GISDATA.TOWNS_POLY in black outline doesn't, since the orange for that is fill.

starting off then:  2 orange layers and 1 black (in the active datalayer)

(see attachment)

If I make a small selection box for the snapping area the features to snap too 
are only orange.

(see attachment)

Do we need to see all this orange?  I think it might be best if none of that 
were drawn - it can't be turned on and off, it's getting in the way of my other 
symbology sometimes. 

Perhaps those are the real layers being edited, and the ones I add through the 
folderset are somehow different.  
But I have control over the symbology of those and the users can turn them on 
and off. 
For example, in this real app you'll see the editable lines (here 911 Streets 
to Edit) flash orange at first, before they're covered up by my preferred 
symbology as the thick red lines:
http://maps.massgis.state.ma.us/map_ol_mop/911.php?lyrs=911%20Streets%20to%20Edi
t~massgis:SETB.STREETS_911_TO_EDIT|NavTeq%20MA%20State%20Highways~massgis:GISDAT
A.NAVTEQRDS_ARC_STATE|NavTeq%20MA%20US%20Highways~massgis:GISDATA.NAVTEQRDS_ARC_
US|NavTeq%20MA%20Interstate%20Highways~massgis:GISDATA.NAVTEQRDS_ARC_INT|MSAG%20
Boundaries~massgis:SETB.MSAG_BOUNDARIES_POLYM_911|Massachusetts%20Towns%20Survey
%20Boundaries%20for%20911~massgis:GISDATA.TOWNSSURVEY_ARC|911%20Streets%20to%20E
dit~massgis:SETB.STREETS_911_TO_EDIT|911%20Streets~massgis:SETB.STREETS_911|Mass
DOT%20Roads%20Route%20Numbers%20Max%20150000~massgis:GISDATA.EOTROADS_ARC&bbox=-
71.21213302013777,42.39103946911365,-70.93489989640825,42.462250711325595&coordU
nit=m&measureUnit=m&base=googleSatellite&center=-7911867.6610223,5225106.1401293
&zoom=6 

which is OK in this example, but when the snapable layers start becoming orange 
too things seem to get out of hand.. 

Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 14 Sep 2011 at 8:20

Attachments:

GoogleCodeExporter commented 9 years ago
I've changed the setup of the tools so that the layers only turn orange when 
they're actually *being edited*, rather than just being on and orange all the 
time.

I've also added an enhancement so that you can set the "editing" color via the 
"color" property of an editconfig in the tool_configs.js file.

Original comment by its.s...@gmail.com on 13 Oct 2011 at 9:54

GoogleCodeExporter commented 9 years ago
The orange seems to be gone but I can't find the reference to the "color" 
property.
Has nothing been added to the toolConfig_default.js yet to demonstrate this? 

Original comment by Aleda.Fr...@state.ma.us on 19 Oct 2011 at 8:51

GoogleCodeExporter commented 9 years ago

Original comment by Aleda.Fr...@state.ma.us on 4 Nov 2011 at 8:31