https://bugs.documentfoundation.org/show_bug.cgi?id=62196
V Stuart Foote <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|EDITING: copy-paste from |EDITING: copy-paste from |non-LibO-text-source pastes |non-LibO-text-source pastes |previous clipboard contents |previous clipboard contents | |(see comment 28, comment | |31, comment 38) --- Comment #62 from V Stuart Foote <[email protected]> --- (In reply to Joel Madero from comment #61) can't blame volunteers for what interests them and what doesn't). > > One thing to try (I haven't read 60+ comments of this thread so maybe it's > already been suggested) is to actually analyze what is in your clipboard > using something like this: > > http://www.thewindowsclub.com/windows-clipboard-manager-viewer > > Just verify that your clipboard in fact only has a single thing and that the > paste into LibreOffice does not match it. > > Also maybe try an alternative clipboard manager: > http://www.makeuseof.com/tag/3-clipboard-managers-windows/ Actually this is the wrong approach. The issue on Windows more often than not is the presence of 3rd party apps that muddle control of MS Windows Clipboard APIs. The Windows clipboard is stateful -- one app at a time has control of writing to and reading from, as well disposing its buffered content. LibreOffice has internal clipboard structures (XClipboard based) which are then interfaced to the MS Windows APIs. In fact, LibreOffice XClipboard tries to play nicely with the OS clipboard--gaining control and releasing when it is called back. Problems happen for us when other programs are not so fastidious. Windows OS memory and clipboard managers are some of the worse offenders in that regard. (See comment 28 comment 31 comment 38) What is likely needed within LibreOffice is a refactoring of the XClipboard (and then connecting that to appropriate Linux, OS X and Windows APIs) to include additional UI controls for: 1) our internal clipboard, 2) our interaction with the OS clipboard, 3) an ability to flush internal as well as system clipboard, 4) an ability to reegain/lock access/control of the system clipboard, 5) a GUI panel (probably on the Sidebar) to display the clipboard object stack. All of which are clearly an enhancement--which this issue is not. And, this issue should be Closed Insufficientdata as the OP has yet to respond about specific issue as titled--and the later issues remain too spurious and nonreproducible with out STR as to be valid. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
