Project

General

Profile

bug #7990

Moving a feature via d&d does not make the Feature Tree Editor dirty

Added by Andreas Müller about 2 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Highest
Assignee:
Katja Luther
Category:
taxeditor
Target version:
Release 5.19
Start date:
01/14/2019
Due date:
% Done:

0%

Severity:
normal
Found in Version:
Tags:
additivity

Description

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.

Related issues

Related to Edit - feature request #7873: Implement copy&paste for feature nodes in feature tree editor Closed 10/26/2018
Duplicated by Edit - bug #8021: d&d in feature tree editor should not require saving Duplicate 01/27/2019
Duplicates Edit - bug #8774: Reimplement term tree editors to implement the general save strategy Closed 12/17/2019

History

#1 Updated by Andreas Müller about 2 years ago

#2 Updated by Andreas Müller about 2 years ago

  • Duplicated by bug #8021: d&d in feature tree editor should not require saving added

#3 Updated by Patrick Plitzner about 2 years ago

  • Priority changed from New to Highest

#4 Updated by Patrick Plitzner about 2 years ago

  • Tags set to additivity

#5 Updated by Patrick Plitzner about 2 years ago

  • Target version changed from Release 5.6 to Reviewed Next Major Release

#6 Updated by Andreas Müller over 1 year ago

  • Target version changed from Reviewed Next Major Release to 287

#7 Updated by Andreas Müller over 1 year 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.

#8 Updated by Andreas Müller about 1 year ago

  • Target version changed from Release 5.13 to Release 5.14

#9 Updated by Andreas Müller about 1 year ago

  • Target version changed from Release 5.14 to Release 5.15

#10 Updated by Katja Luther 11 months ago

  • Target version changed from Release 5.15 to Release 5.18

#11 Updated by Katja Luther 11 months ago

  • Target version changed from Release 5.18 to Release 5.15

#12 Updated by Andreas Müller 10 months ago

  • Target version changed from Release 5.15 to Release 5.18

#13 Updated by Katja Luther 4 months ago

  • Target version changed from Release 5.18 to Release 5.19

#14 Updated by Andreas Müller 4 months ago

  • Status changed from New to Feedback

Is this still an open issue with the new term tree implementation? If not we should close it as works for me or as duplicate for the term tree ticket.

#15 Updated by Katja Luther 4 months ago

  • Status changed from Feedback to Closed

ups no, this issue is solved with the new implementation.

#16 Updated by Andreas Müller 4 months ago

  • Duplicates bug #8774: Reimplement term tree editors to implement the general save strategy added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)