Understood; as this section of the code has fallen into technical debt perhaps
you can fix these ones interactively without going through the full proposal
process?
I would recommend using an Enum rather than int for example :-)
I do note that the layer changed( int ) is designed to be open ended so you can
communicate additional ideas here (filter, style etc...).
--
Jody Garnett
On Friday, 15 April 2011 at 12:48 PM, Michael Bedward wrote:
> Hi Jody,
>
> > I will look for you on IRC; I am not sure I can answer without the code in
> > front of me and an understanding of the problem.
>
> Thanks - that would be good. No rush.
>
> > I do note that Layer has all the fire utility events that are needed:
> > - fireMapLayerListenerLayerChanged(int)
> > - fireMapLayerListenerLayerShown()
> > - fireMapLayerListenerLayerHidden()
> > - fireMapLayerListenerLayerSelected()
> > - fireMapLayerListenerLayerDeselected()
>
> This is where the old vs new mismatch starts to creep in. The methods
> for selected are out of date since there is no longer a selected flag.
> I'd like to cater for "filter changed", "style changed" without
> bunging them all into "layer changed". And it would be nice to have
> changes to the new user data element trigger events too. So I'm keen
> on clean-up before hook-up :)
>
> Michael
>
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
