fredsa / gwt-dnd

Library providing easy to use mouse or touch based drag-and-drop capabilities to GWT
42 stars 41 forks source link

draggable panel body must be dragged entirely outside of its previous location #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Use 'getting started' code base
2. add targetpanel to a panel that is draggable
3.

What is the expected output? 
Because draggable panel is withing Absolute panel should be able to be
dragged, and released anywhere within absolute panel.

What do you see instead?
draggable panel body must be dragged entirely outside of it prevoius
location to be dropped

What version of the product are you using? On what operating system?
gwt-dragdrop-2007-04-17.jar, Ubuntu OS.

Please provide any additional information below.

Original issue reported on code.google.com by matt.and...@gmail.com on 19 Apr 2007 at 10:32

Attachments:

GoogleCodeExporter commented 9 years ago
stupid online summary! and I can't edit it to fix it!

Original comment by matt.and...@gmail.com on 19 Apr 2007 at 10:34

GoogleCodeExporter commented 9 years ago

Original comment by fredsa on 19 Apr 2007 at 11:22

GoogleCodeExporter commented 9 years ago

Original comment by fredsa on 19 Apr 2007 at 11:22

GoogleCodeExporter commented 9 years ago
In 
http://groups.google.com/group/gwt-dnd/browse_thread/thread/513fc699b4dda221/ 
you
had reported a problem whereby a drop target was also itself draggable. That 
issue
was fixed in r186.

You've now run into a more general problem whereby a drop target is the child of
another draggable. The draggable disappears on drop as it tries to attach 
itself to
the drop target.

This issue fixed in r194.

Original comment by fredsa on 20 Apr 2007 at 3:38

GoogleCodeExporter commented 9 years ago
In 
http://groups.google.com/group/gwt-dnd/browse_thread/thread/513fc699b4dda221/ 
you
had reported a problem whereby a drop target was also itself draggable. That 
issue
was fixed in r186.

You've now run into a more general problem whereby a drop target is the child of
another draggable. The draggable disappears on drop as it tries to attach 
itself to
the drop target.

This issue fixed in r194.

Original comment by fredsa on 20 Apr 2007 at 3:39

GoogleCodeExporter commented 9 years ago

Original comment by fredsa on 23 Aug 2007 at 3:38