U++ forum: Welcome to the forum

Re: DragAndDrop FILES does not work under LINUX [message #35008 is a reply to message #35007]

Tue, 27 December 2011 21:49

Didier
Messages: 680
Registered: November 2008
Location: France

Contributor

I tested with gnome and it also works fine,

Seems to be a KDE specific problem

But looking at the logs in DEBUG mode

In GNOME:

#### PasteClip = 
Target action 1
Sending status/finished to 23115959 accepted: true
DropStatus Client Message XdndPosition
Client Message 83890900 XdndPosition, src: 23115959
XdndPosition [757, 350], action XdndActionCopy
Source action 1
#### PasteClip = 
Target action 1
Sending status/finished to 23115959 accepted: true
DropStatus Client Message XdndPosition
Client Message 83890900 XdndPosition, src: 23115959
XdndPosition [759, 352], action XdndActionCopy
Source action 1
#### PasteClip = 
Target action 1
Sending status/finished to 23115959 accepted: true
DropStatus Client Message XdndPosition
Client Message 83890900 XdndPosition, src: 23115959
XdndPosition [760, 353], action XdndActionCopy
Source action 1
#### PasteClip = 
Target action 1
Sending status/finished to 23115959 accepted: true
#### PasteClip = 
#### PasteClip = 
#### PasteClip = 
#### PasteClip = 
#### PasteClip = 
DropStatus Client Message XdndDrop
Client Message 83890900 XdndDrop, src: 23115959
XdndDrop to 10VMLineEdit : 0xbf82c308(parent 16WithTabDocLayoutIN3Upp10ParentCtrlEE)
Source action 1
#### PasteClip = 
Target action 1
Sending status/finished to 23115959 accepted: true
DropStatus Client Message WM_PROTOCOLS
DropStatus Client Message WM_PROTOCOLS
DropStatus Client Message WM_PROTOCOLS

In KDE

DropStatus Client Message XdndPosition
Client Message 85985289 XdndPosition, src: 81788964
XdndPosition [1023, 365], action XdndActionMove
Source action 2
#### PasteClip = 
Target action 2
Sending status/finished to 81788964 accepted: true
#### PasteClip = 
#### PasteClip = 
DropStatus Client Message XdndPosition
Client Message 85985289 XdndPosition, src: 81788964
XdndPosition [1023, 365], action XdndActionMove
Source action 2
#### PasteClip = 
Target action 2
Sending status/finished to 81788964 accepted: true
#### PasteClip = 
#### PasteClip = 
#### PasteClip = 
#### PasteClip = 
DropStatus Client Message XdndPosition
Client Message 85985289 XdndPosition, src: 81788964
XdndPosition [1023, 365], action XdndActionMove
Source action 2
#### PasteClip = 
Target action 2
Sending status/finished to 81788964 accepted: true
#### PasteClip = 
#### PasteClip = 
#### PasteClip = 
DropStatus Client Message XdndDrop
Client Message 85985289 XdndDrop, src: 81788964
XdndDrop to 10VMLineEdit : 0xbfb1fde8(parent 16WithTabDocLayoutIN3Upp10ParentCtrlEE)
Source action 2
#### PasteClip = 
Target action 2
Sending status/finished to 81788964 accepted: true
DropStatus Client Message WM_PROTOCOLS
DropStatus Client Message WM_PROTOCOLS
DropStatus Client Message WM_PROTOCOLS

The target action differs: 1 in GNOME and 2 in KDE
You are certainly right saying it's a protocol problem.
Where is all this protocol parsing done, i can try and take a look at what can be done ?

Report message to a moderator