[Libreoffice-bugs] [Bug 106973] Dragging FileList out of LO fails

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Tue Apr 25 07:37:44 UTC 2017


https://bugs.documentfoundation.org/show_bug.cgi?id=106973

christian.rufener at actelion.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |UNCONFIRMED
     Ever confirmed|1                           |0

--- Comment #3 from christian.rufener at actelion.com ---
I think the LO UNO API does not work as expected:
The receiving (Windows) application (e.g Explorer, Wordpad) gets the WM_DROP
message, but when it is calling WIN32 API DragQueryFiles to get the list of
dropped files, the (receiving) application crashes. I assume this is due to the
fact that the passed data structure from LO is invalid.
As I understand the "getTransferData" needs to return a byte[] containing the
list of files separated by a null byte(character?) and needs to be terminated
by a null byte/character. This is what the WIN32 documentation claims. And this
is what I get the other way around: If files are dropped to my LO extension,
they're separated by a (byte)0.
I tried a lot of combinations of byte[] to be returned but never succeeded in
any reasonable behavior. I tried to return wrapped byte[] in an Any or raw
byte[]. 
Returning anything else e.g. char[] would not lead to any WM_DROP message at
all, so I assume it needs to be byte[], which is what the LO UNO documentation
says anyway.
Searching for documentation/example which demonstrated this was unsuccessful.
Looking at the LO source code did not reveal any more clues.

I was hoping to get some hints by filing this issue.

Regards
Christian

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20170425/7728b683/attachment.html>


More information about the Libreoffice-bugs mailing list