What's new in gwt-dnd-2.5.6.jarBug Fixes- Removing final scroll panel workarounds which have been obsoleted by recent GWT 1.5 coordinate system fixes. Thanks Carolin Nolte!
What's new in gwt-dnd-2.5.5.jarUseful hosted mode checks that tend to bite a lot of developers- Add boundary panel clientHeight == 0 check in hosted mode, mostly to catch standards rendering mode BODY client height == 0
- Add hosted mode check for GWT issue 1813 RootPanel.get("id") does not apply position: relative to element
What's new in gwt-dnd-2.5.4.jarBug Fixes- Fix for issue 45 , correcting problems with draggable images in IE when drag sensitivity > 5. Thanks Tim Valenzuela!
Other updates- Corrected exception message in PickupDragController#saveSelectedWidgetsLocationAndStyle(), as reported in issue 41 . Thanks ToonTalk!
What's new in gwt-dnd-2.5.3.jarBug Fixes- Correctly handle VetoDragException in onPreviewDragStart(). Thanks yogesh17.patel!
- Correct ScrollPanel offsets for drop target inside a split panel. Thanks Markus (coware.de)!
- Fixed width of spacer in IndexedPanelExample demo so you can more easily drop on an "empty" column. Thanks Vitaly.Sazanovich!
API additions- Added DragController#getBehaviorCancelDocumentSelections and DragController#setBehaviorCancelDocumentSelections
Other updates- Add history token support to demo
What's new in gwt-dnd-2.5.2.jarBug Fixes- Corrected handling of ScrollPanel calculations for indexed panels. If you wrap your drop targets in scroll panels, this fix is for you. Thanks markwmccall!
Other updates- Ant build script fixes. Thanks A.A.Vasiljev!
What's new in gwt-dnd-2.5.0.jarChanges in this release- Java 1.5 / GWT 1.5 support
- Removed previously deprecated methods
Bug Fixes- FlowPanelDropController, with a PickupDragController and no drag proxy, dragging a widget to the same FlowPanel that it started in. If you then throw a VetoDragException from a FlowPanelDropController the widgets are restored to the wrong location. Thanks dunhamsteve!
- Issue 24: Scroll panels (actually any offset parent elements are now taken into account when considering drop target intersection with the mouse cursor.
- When dragging quickly with non-zero drag sensitivity, drag may not start until mouse later wandered back over widget. Thanks amralam!
- Once multiple widgets have been selected, clicking on one, without the CTRL/meta key, removed the remaining widget, if an AbstractIndexedDropController was in use. Thanks bosco!
- Dragging multiple widgets from a flow or indexed panel, caused them to be dragged with incorrect relative positions. Thanks bosco!
- Indexed panel draggable swapping positions with next widget at the start of a drag. Thanks aholub & bosco!
Other updates- Ant build changes. Thanks janek.bogucki!
- Added a NOTICE file; See this project's Apache 2.0 License for what this means if you want to redistribute gwt-dnd
- Removed workarounds for issues resolved in the 1.5 milestone
- Javadoc updates
- Optional debug code for DOMUtil#findIntersect, which can be enabled by setting DOMUtil.DEBUG to true
public static final boolean DEBUG = true; Minor updates to online demos
What's new in gwt-dnd-2.0.7.jarBug Fixes- Fixed drop target eligibility sorting, especially for more complex client applications, especially if your application has a mixture of drop targets that have ancestor/descendant DOM relationships, and drop targets that do not
- Workaround to prevent the occasional "Unknown runtime error" in IE at the start of a drag
- DragEndEvent#getDropTarget() would throw NullPointerException when referenced from DragHandler#onDragEnd(). Thanks sfranciscus!
Changes in this release- Drag Handlers will now have onPreviewDragEnd() called, even if a drop controller already vetoed the drag operation
- Drag handlers will now see the same DragEndEvent instance in onPreviewDragEnd() and onDragEnd(), and the same DragStartEvent instance in onPreviewDragStart() and onDragStart()
- Cleaned up DragEndEvent#toString() and DragStartEvent#toString() output
- CSS margin: 0px is now always set during dragging so that stylesheet based margins are also overridden; previously only margins set explicitly on the DOM element would be overridden
- context.draggable is now reset to null after drag operations end
- DragController#resetCache() may now be called when no drag is currently underway, allowing for simplified client code in some use cases
Other updates- New PaletteExample in the interactive demos
- Implementation changes, moved some cleanup code from MouseDragHandler to DragContext
- Modified implementation of DragHandlerCollection
- Updated ant build file and other Eclipse project files
What's new in gwt-dnd-2.0.5.jarBug Fixes- Issue 21 Mac users can use the option/meta key for multi-select. Thanks binduwavell!
Changes in this version- AbstractIndexedDropController#newPositioner(DragContext) access changed from default to protected to allow subclasses to override the default implementation. Thanks martijn.spronk!
What's new in gwt-dnd-2.0.4.jarChanges in this version- Rebuilt jar file to target JDK 1.4 (Java *.class file version 48.0). Previous jar was inadvertently packaged with version 50.0 (Java 6) *.class files.
What's new in gwt-dnd-2.0.3.jarChanges in this version- The AbstractDragController constructor no longer accepts null as a value for the boundaryPanel parameter. Client code must instead pass in RootPanel.get() explicitly. Tis is actually a documentation change, as null did not work in gwt-dnd 2.0.2 either.
- The current gwt-dnd version is available via $GWT_DND_VERSION, once the gwt-dnd classes have been (statically) initialized. This also means you can grep the JavaScript compiled output for GWT_DND_VERSION.
- Added two !important CSS rules for the HTML element, HTML { margin: 0px !important; border: none !important; } , as a workaround for GWT Issue 1932.
Bug Fixes- Corrected dragging positions when the document BODY (RootPanel.get()) has non-zero CSS margins/borders and is used as the drag controller boundary panel.
What's new in gwt-dnd-2.0.2.jarFeature Highlights- Select multiple widgets for dragging via CTRL/META-click. Use DragController#setBehaviorMultipleSelection(true) to enable this functionality.
- Drop target selection and drop positioning are based on the current mouse location rather than current draggable location/center. This has been much requested, and makes gwt-dnd more consistent with traditional desktop drag-and-drop behavior.
- Drag behavior is more configurable.
- An updated API (to support the above).
API Considerations- If you are starting a new project, please use the latest gwt-dnd 2.x APIs so that you benefit from all the latest features and fixes.
- If you have an existing project using gwt-dnd 1.x, you may wish to remain on gwt-dnd 1.x until you have a pressing need to migrate to gwt-dnd 2.x, such as the requirement to be able to drag multiple widgets at once.
- If you plan on migrating from 1.x to 2.x, please see the APIMigrationGuide_v1_to_v2 wiki for details.
Bug Fixes- As a workaround for a bug that causes IE6 to crash, mouse events are internally tracked on a separate capturing widget, rather than on the panel being dragged.
What's New in gwt-dragdrop-1.2.6.jarBug Fixes- Fix for Error: TYPE_MISMATCH_ERR: DOM Exception 17 with Safari 3.0.4 (5523.10) on Mac OS X Version 10.5 (Leopard). This was caused by the code to cancel the current text selection at the start of each drag operation.
What's New in gwt-dragdrop-1.2.5.jarBug Fixes- When two draggables were in close proximity one could sometimes mouse down on one widget, but move quickly enough that the second widget received the first mouse move event. This would cause the second widget to be dragged instead of the first. Fixed so that the widget on which you mouse down is always the one that is dragged.
New Features- While the positioner (usually the dashed light blue rectangle) was always constrained to the boundary panel, the draggable or its drag proxy could be dragged outside of these borders. One can now call DragController#setConstrainWidgetToBoundaryPanel(true) to change this behavior.
Other Changes- Eligible drop targets are once again sorted based on their relationship in the DOM, rather than on their relative size, this time using the suggestion in GWT issue 1218.
- Demo classes no longer depend on gwt-log as this was throwing a few too many people off. A light weight replacement UnCaughtExceptionHandler is used instead.
- Some of the online demos have been updated
Other Changes from earlier releases- See the change log for all the details. Thanks Conzar, Michael Speth and Stephen Sanders of opnet.com, fameeda.tamboli (synerzip.com), buelltm, jonathan.dudley, jsjenkins168, iamroberthanson, rohitsghatol, ryan.detert, Peter.Dobratz, mwaschkowski, Marcos, matt.andruff, skaflotten, Peter.Dobratz, matthiasthoma, boscomonkey and Mario Zenadocchio!
What's New in gwt-dragdrop-1.2.4.jar- Release 1.2.4 is not new. It's old :).
|
Sign in to add a comment
Hi, I noticed that you addressed the TYPE_MISMATCH_ERR: DOM Exception 17 error in Safari. You mentioned that it was related to the ondragstart related code and canceling the text selection. Do you have any more details. I looked at the SVN, but I'm not familiar enough with the projec to find the areas that you updated. Thanks, Nathan
I believe it had to do with window.getSelection().collapse() no longer working in Safari 3.0.4
I have found this 'window.getSelection().collapse() no longer working in Safari 3.0.4' too.
Is there a work around? A fix?
Simply upgrade to the latest gwt-dnd version, and the Safari 3.0.4 issue will be resolved.