Xopus 3.2.4 Drag and drop problem

September 20 2007

  • 6 replies.
  • This question is not yet resolved.
  • This question was started by Helena.
  • Last post by Helena.
Helena
user
September 2007, 16:07
Hi all,
I have just installed version 3.2.4 and it is very nice, especially the drag&dropping.
But I have a small problem, I cannot drag&drop my <img> elements.
Basically I have a <p> element which can contain
<xs:element ref="b"/>
<xs:element ref="i"/>
<xs:element ref="a"/>
<xs:element ref="br"/>
<xs:element ref="img"/>
elements.
I am able to drag&drop the other elements, but not the <img> element. (I want to drag&drop this into another <p> element, so the schema should allow this.

Salar
Xopus Team
September 2007, 17:20
Hi Helena,

I'll have to look in to your specific case. Could you send it to us through the reproducer (ctrl+alt+R)?
Helena
user
September 2007, 10:06

Case 38833

I created a case
Salar
Xopus Team
October 2007, 17:26
Hi Helena,

I just looked in to it. You can't drag & drop the images in your case because of your XSL: every image is surrounded with contenteditable="false" (line 256). This makes it impossible to select the image for any operations, including drag & drop.

Is there a specific reason for using contenteditable="false"?
Helena
user
October 2007, 11:38

contenteditable="false"

Well I put this div, because the image has an onclick event (the user can change the linked image) and our users did not like the "four way" cursor that is displayed by default when hovering over an image. They thought that this cursor does not make it clear that you can click on the image and thus change it.
The div allowed me to display the cursor our users like (the "pointer" cursor).
What options are there? Tell our users "if you want to drag&drop you have to put up with this cursor" or "have the nice cursor but not the drag and drop functionality" or do you have any other solution?
Thanks
Helena

Helena
anonymous user
October 2007, 11:59
I just found out that removing the div also resolves my problem with:
http://xopus.com/RDB/topic/101.new
and corresponding case: 38454 as you hinted that no selection is possible (and it might resolve another small problem I have, which is also linked to the fact that the users wanted a special cursor)
I also have a button that insert a clickable link (this link cannot be modified (neither the content, nor the attributes) so I also put a div around it, and added the "hand" cursor. But now we are not able to delete this clickable link as it apparently cannot be selected (the context menu does not propose the "delete" option.
So I was wondering, how can I solve my dilemma of having a content-editable=false element but still be able to select it?
Helena
anonymous user
October 2007, 12:02

http://xopus.com/devblog/2007/craziest-dhtml-hack-ever

Just found this: it kind of explains my dilemma ;-)


React

HTML will be shown as HTML code.
Linebreaks and Links starting with http:// are automatically resolved