Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353284

Summary: GANTT DND between GanttGroups
Product: z_Archived Reporter: Johan Schulz <schulz.johan>
Component: NebulaAssignee: Emil Crumhorn <emil.crumhorn>
Status: CLOSED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: reichljuergen
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Johan Schulz CLA 2011-07-28 03:41:36 EDT
Build Identifier: M20110210-1200

There is currently only dragging between sections implemented. Any plans on implementing DnD between GanttGroups?

We use the GanttChart in a tree like model

Section A
   |_ GanttGroup -> [GanttEvents]
   |_ GanttGroup -> [GanttEvents]
   |_ GanttGroup -> [GanttEvents]

Section B 
   |_ GanttGroup -> [GanttEvents]
   |_ GanttGroup -> [GanttEvents]
   |_ GanttGroup -> [GanttEvents]

and want to drag e.g. one event from section B group 1 to section A group 2. 
Currently there is no chance to identify an GanttGroup, so my first enhancement would be to add either an _data object to GanttGroup or at least an _id field to find the correct group later on.


The problem arises in GanttComposite.getSurroundingVerticalEvents if you have all your events organized in above structure because there is no check if the IGanttChartItem is an GanttGroup. All events are casted to an GanttEvent and so he cant find out the top element. This causes some NPE later on.

So either add checks and disallow dragging or if possible add DnD capabilities for groups :)
+1 for second 



Regards

Johan






Reproducible: Always

Steps to Reproduce:
1. create event structure described in details
2. allow dragging between sections
3. drag one event from one group in a section to another section
Comment 1 Wim Jongman CLA 2019-12-12 15:58:25 EST
This bug does not have a target milestone assigned and is automatically closed as part of the 2.3.0 release cleanup.

It could be that this bug is accidentally closed for which we apologize.

If this bug is still relevant, please re-open and set a target milestone.