Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.5
-
Fix Version/s: None
-
Component/s: ICE-Components
-
Labels:None
-
Environment:Operating System: Windows XP
Platform: PC
Description
Need support for dragging and dropping within a tree, from node to node.
Currently, nodes can be dragged but not dropped. Also probably have to do tree
model changes on drag and drop events.
Came up in forum post:
http://support.icesoft.com/jive/thread.jspa?threadID=2303&tstart=0
Currently, nodes can be dragged but not dropped. Also probably have to do tree
model changes on drag and drop events.
Came up in forum post:
http://support.icesoft.com/jive/thread.jspa?threadID=2303&tstart=0
Community member may have found a work-around:
David Lim
Posts: 22
From: Malaysia
Registered: 7/20/06
Read Re: Need help with drag and drop on trees...
Posted: Sep 25, 2006 11:26 PM
Click to recommend this message to become a new knowledge base document. Click
to edit this message... Click to delete this message... Click to branch this
topic starting with this message... Click to reply to this topic Reply
Huh? Really? Not supported? And I thought it was a bug... but I [i]have[/i]
gotten it to work with something like this:
<ice:tree id="tree" value="#
{myBean.treeModel}" var="item" hideRootNode="true"
{styleBean.imageDirectory}hideNavigation="false" imageDir="#
">
<ice:treeNode>
<f:facet name="icon">
{item.userObject.icon}<h:panelGroup>
<h:graphicImage value="#
" />
</h:panelGroup>
</f:facet>
<f:facet name="content">
{item.userObject.name}<ice:panelGroup style="display: inline" draggable="true" dragOptions="dragGhost"
dropValue="#
" dragMask="drag_cancel, dragging, dropped,
{item.userObject.handleDrop}hover_start, hover_end" dropMask="hover_start" dropTarget="true"
dropListener="#
">
{item.userObject.nodeClicked}<h:commandLink actionListener="#
"
{item.userObject.description}partialSubmit="true" value="#
"/>
</ice:panelGroup>
</f:facet>
</ice:treeNode>
Does this change our priority? We don't want to spend a lot of time reworking
the tree component in v1.6 for this feature when it may be re-developed for 2.0
anyway.
Ken