https://issues.apache.org/ooo/show_bug.cgi?id=124085
--- Comment #38 from Armin Le Grand <[email protected]> --- I looked deeper into the clipboard stuff for windows (unified using UNO API implementations) and with deeper understanding found the problem. For mime-type based stuff there is no fixed CF_XYZ ID for the Windows clipboard, but that ID changes with each win restart (probably dependent of who registers it first at the system clipboard). Thus, do not use a fixed ID in the translation table. It would be possible to update that value in the table dynamically when clipboard content is received (at that time there is a match between ID and mime type), but it's all alreday there; just use CF_INVLAID as ID and the correct mime type handling for windows is already in place. I was misleaded niitially by the name of CF_INVLAID; it does not stand for an invalid ID but more for 'this type has no classic CF_XYZ ID'. Checked and works well. Preparing commit. @John: At this point really the file is received from the clipboard (in PNG format, others may follow), thus it would be possible to associate this with the BitmapEx and use that 'original' for exports. Unfortunately all our internal APIs only carry the BitmapEx, so this would be very much work to do here. -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes.
