Yes, but XEmbed isn't known by all client apps, and I have not managed to
get it and other misc. odd behaviors to work correctly when reparenting.
Believe me, I have not forgotten this issue and I have been (aside from the
past couple of weeks when I have been in Toledo) trying to get things to
work properly. This bug will be closed as soon as I possibly can, I am
sorry that it hasn't been done yet, but I have been working on it.
--
Sent from my ADP1 Phone running Cyanogen
On Dec 5, 2009 6:45 PM, "Szunti" <email address hidden> wrote:
"Basically, the embedder has to operate as drag-and-drop proxy for the
client." I think it's the same for other events. (Not if what i think
means anything)
Yes, but XEmbed isn't known by all client apps, and I have not managed to
get it and other misc. odd behaviors to work correctly when reparenting.
Believe me, I have not forgotten this issue and I have been (aside from the
past couple of weeks when I have been in Toledo) trying to get things to
work properly. This bug will be closed as soon as I possibly can, I am
sorry that it hasn't been done yet, but I have been working on it.
--
Sent from my ADP1 Phone running Cyanogen
On Dec 5, 2009 6:45 PM, "Szunti" <email address hidden> wrote:
I don't know these stuff. I just googled a bit in a hope I find standards. freedesktop. org/xembed- spec/xembed- spec-latest. html#id2447278
something useful. About DND the XEmbed specification sais that it's easy
to implement:
(
http://
)
"Basically, the embedder has to operate as drag-and-drop proxy for the
client." I think it's the same for other events. (Not if what i think
means anything)
--
Close button support in AllTray trunk /bugs.launchpad .net/bugs/ 404564You received this bug n...
https:/