Well, I did niot prove actually, but likely is the
Warning: Attempt to copy to unlocked clipboard!
very close to the reason that NEdit shows on alpha-linux.
Running test/Xm/cutpaste/test1 shows this
(null widget): XmClipboardStartCopy(win 0x7000018, clip 0x20143450, time 0)
(null widget): _XmClipboardGetWindowProperty: XmClipboardFail (alloc_size 0)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 80)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 4)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 4)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 4)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 16)
(null widget): XmClipboardCopy(win 0x7000018, item_id 5016, format STRING)
(null widget): _XmClipboardGetWindowProperty: XmClipboardFail (alloc_size 0)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 80)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 4)
Warning: Attempt to copy to unlocked clipboard!
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 16)
(null widget): XmClipboardEndCopy(win 0x7000018, item 5016)
(null widget): _XmClipboardGetWindowProperty: XmClipboardFail (alloc_size 0)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 80)
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 4)
Warning: Attempt to EndCopy an unlocked clipboard!
(null widget): _XmClipboardGetWindowProperty: XmClipboardSuccess (alloc_size 16)
copied: 'text-1' to clipboard
And the actual result of trying to Copy&Retrieve is a failure:
Warning: Attempt to copy to unlocked clipboard!
Warning: Attempt to EndCopy an unlocked clipboard!
copied: 'text-1' to clipboard
Status was XmClipboardNoData
Someone with an idea what to look for?
--
Alexander Mai
[EMAIL PROTECTED]
