Thankyou, that was all I needed to know. Luckily drag-drop operations are rare and until a new version of Qt comes out all I need to do is create a new workspace and attach the window to the new workspace then do the drag-drop operations in the workspace. I can probably make a macro to do this.
On Fri, 22 Jul 2005 11:16 pm, Tuomo Valkonen wrote: > On 2005-07-22, Lithion <[EMAIL PROTECTED]> wrote: > > Hi, > > I am a user of KDE applications, but have found that drag-drop > > operations do not work for many KDE applications when multiple > > applications are contained in the one frame. > > This is a bug in Qt and has been "fixed" in cvs or whatever it is > that they use AFAIK. The problem is that they don't really check in > what window within the WM frame stuff was dropped on, but simply take > the topmost-stacked window to be it. (Subwindow lists from X are > ordered by stacking). However, most programs (including xprop and > xwininfo) equally stupidly take the lowest-stacked window, and Ion > arranges for the visible main window to be lowest-stacked. (This is > also why xprop et all don't work on transients.) Anyhow, Qt should > have been at least "fixed" to behave brokenly similarly to other > apps. Or maybe it's been properly fixed to actually find the target > window on the list, I don't know.
