Introduce standalone mode for ModifyFeature control

[ahocevar]

In some configurations, the selectControl integrated in Control.ModifyFeature may be undesired. Instead, someone might just want to start mofifying a feature by saying

modifyControl.selectFeature(feature);

Attached is a patch which introduces a standalone property. If set, no selectControl will be created.

[ahocevar]

standalone property for the ModifyFeature control

[tschaub]

This is nice. I added a bit in the deactivate method so that unselectFeature is called if a feature is currently being modified. This is effectively what happens in the non-standalone mode (when the selectFeature control is deactivated). Though an app developer may be able to manually call selectFeature and unselectFeature to start and stop feature modification - I think it is important that the control cleans up after itself on deactivation (and the app developer may not be able to intervene here.)

The tests demonstrate what happens. There is currently no "beforefeaturemodified" event triggered. It may make sense to trigger this (and respect the return) in selectFeature in standalone mode (so feature modification can be stopped at the application level).

Andreas, if you agree the change I made is good, please commit. I confirmed that tests pass in FF3 - didn't check IE.

[tschaub]

standalone mode for modify feature control

[ahocevar]

r9591