Is there "some way" to keep polling who has/gets the clipboard lock?
No, I attempted to implement that, but getting the window title from the hwnd proved futile.
I trust you; I've been trying to enumerate what windows could a PID or any of its parents' own (without starting by iterating through all the windows).
However, "for now", could the list contain PIDs and pid_name? Not as useful, but maybe helpful enough.
"Later", if good ideas come, it could be amended.
Can you add diagnostics "of a higher level" than normal diagnostics, that would show:
Not really, it's in there already.
clipboard sync start
Two options:
- the other end is asking for clipboard data:
process_clipboard_packet: clipboard-request
- we have new clipboard data to send:
clipboard event: CLIPBOARDUPDATE
followed by clipboard_send: clipboard-contents
clipboard sync done
We have: SetClipboardData(..) done
That's for win32, X11 looks very different.
My issue here is that sometimes debug logs raise the cognitive load too much for me when I try to read them.
I mean, you can argue "it's none of your business as end-user" and that's end of discussion.
However, in this context, in this specific situation, it would be much easier for me to see that "yes, I did press Ctrl+C" and something happens, but OOPS. Also, these extra logs are ~200 lines; in my head, would be seeing 2 lines (or 5 or 10 depending on "how" this works).
copyleft 2010 - 2020
