[OpenLayers-Dev] Questions about onFeatureInsert() and Features.state

[Niklas Ringdahl]

I am editing features in a Vector layer and discovered that there are some
gaps in the logic in Vector.js. It turns out that Jean-Christophe posted on
this a while ago, would it be possible to change Vector.js per his request?
It would improve the editing flow very much. Or should I post a suggestion?
We have been in contact with Tim Schaub on the "deleted features" matter
mentioned below, and I think there will be a patch on that soon, but I am
not sure about that.

I am quite new to the Open Source domain, so I am not sure of how I am
expected to act upon a change request. Shall I post a suggested new version
of Vector.js?

Best regards,
- Niklas


jc A wrote:
> 
> A remark about OpenLayers.Feature.Vector.state :
> 
> In OpenLayers.Feature.Vector.initialize(..) Line ~50
> this.state should be initialized like :
> this.state = OpenLayers.State.UNKNOWN;
> 
> Or, in the function toState(..) you should add a 'defaut:' at lines ~213
> and ~234 to manage the case where : this.state is null
> 
> ---
> 
> And the last question :
> 
> Is it possible today to not draw (hide) a  'deleted' feature ?
> I mean a feature where feature.state is OpenLayers.State.DELETE ?
> 
> 
> Regards.
> 
> Jean-Christophe ALBERT
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 	
> 
> 	
> 		
> ___________________________________________________________________________ 
> Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
> ! 
> Profitez des connaissances, des opinions et des expériences des
> internautes sur Yahoo! Questions/Réponses 
> http://fr.answers.yahoo.com
> _______________________________________________
> Dev mailing list
> Dev at openlayers.org
> http://openlayers.org/mailman/listinfo/dev
> 
> 

-- 
View this message in context: http://n2.nabble.com/Questions-about-onFeatureInsert%28%29-and-Features.state-tp1832737p2358117.html
Sent from the OpenLayers Dev mailing list archive at Nabble.com.