Because your company makes you use Azure Virtual Desktop to connect to a VM and AVD’s clipboard handling is as unreliable as anything else from Microsoft?
If you’ve ever looked at windows desktop application source code (shudder) they have all this wacky shit around event handling in their native C/C++ APIs, which is a lot less clean that what you typically see in other languages / platforms which do similar event handling. It wouldn’t surprise me if that shit is hacky and buggy as fuck on the OS side of that implementation too.
So this would be your ctrl-c press event, and whatever handler code.
Though it’s been like 20 years since I looked at some of this. Maybe it’s better now, but somehow I doubt it.
My C and V key are literally the most worn keys on my keyboard. The letters are completely worn off, they’re by far my most used keys. That amount of use probably makes the contacts degrade and less reliable.
Windows 10 (I think?) introduced a “fancy clipboard” with history and multi paste and generally made it an “app”. In my experience the fancier it is the more failure points, since it’s no longer just a simple OS memory buffer, it has its own application logic.
Since it’s a global hotkey, the OS has to:
Handle the interrupt
Query the currently active window / application for a “copy” output of the currently highlighted context
Wait for a response
Place that response into a buffer of some sort
In a highly volatile asynchronous UI where the user can alt tab at any time, I imagine often what happens is that you just didn’t wait long enough for the data to actually copy. Pressing CTRL+C would be equivalent in reliability as waiting 2 seconds, but it’s more fun to press the button a bunch
Nah that’s not at all how that hand movement works. It’s always rest on Ctrl and then find C for me. It would also type “C” over the highlighted text, which would be very noticeable.
No that’s not what I mean (plus it doesn’t work most of the time, either). It’s the copying that often fails for me, which I only notice when I paste and realize “wait a minute, these are the previous contents of the clipboard.”
FACT.
Does anyone here know why it’s unreliable?
Windows.
Because your company makes you use Azure Virtual Desktop to connect to a VM and AVD’s clipboard handling is as unreliable as anything else from Microsoft?
That’s a sensible theory for when this happens at work (it’s Citrix in my case).
I’d swear it happens at home on Windows 10 as well, though. Maybe I am pressing it wrong sometimes. Either way, the meme is spot on for me.
It wasn’t always like this.
I swear every version of Windows between 3.11 and XP was 100% reliable. Then it just started… slipping.
What’s weird is that it often works on the second try.
If you’ve ever looked at windows desktop application source code (shudder) they have all this wacky shit around event handling in their native C/C++ APIs, which is a lot less clean that what you typically see in other languages / platforms which do similar event handling. It wouldn’t surprise me if that shit is hacky and buggy as fuck on the OS side of that implementation too.
So this would be your ctrl-c press event, and whatever handler code.
Though it’s been like 20 years since I looked at some of this. Maybe it’s better now, but somehow I doubt it.
I have unconfirmed theories.
Probably just because you typed C + Ctrl by accident.
Nah that’s not at all how that hand movement works. It’s always rest on Ctrl and then find C for me. It would also type “C” over the highlighted text, which would be very noticeable.
Yeah, I guess it would type a C.
Maybe your keyboard lacks NKRO and your cat was sitting on 6 other keys? =P
Because copy and paste started bring over formatting.
If you do control shift V, it removes it and is much more reliable.
No that’s not what I mean (plus it doesn’t work most of the time, either). It’s the copying that often fails for me, which I only notice when I paste and realize “wait a minute, these are the previous contents of the clipboard.”