Moving a feature via d&d does not make the Feature Tree Editor dirty
This is because moving feature currently requires prior save and the move operation is handled server side.
As the Feature Tree Editor is not a pure navigator and appears in the Editor part (in the middle) this is unepected behavior. We need to discuss want the best behavior is, either we implement d&d as client side action or we make the Feature Tree Editor more a navigator whith more separated functionality for editing a node and moving nodes as it is in taxon navigator.
#7 Updated by Andreas Müller about 1 month ago
- Assignee changed from Patrick Plitzner to Katja Luther
- Target version changed from 287 to Release 5.13
In general the feature tree editor should persist data only after pushing save and therefore needs to be refactored. Feal free to open a new ticket or handle this in this ticket, too.