The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I'm using ClipX 184.108.40.206 beta 7 x64 (Jul. 6th, 2008) and it happens occasionally that it stops receiving the clipboard data or it completely crashes. It worked perfectly in Win7, but it stopped in Win10.
Anyway do you use 32bit 3.8 in 64 bit environment and everything works?
In my novice days - mid-1980s, before Windows had become dominant on the desktop - I was working on an office automation suite. We introduced a clipboard mechanism with multiple clips, but the customers found it to complex in use. They were asking us to make something simpler, like what they had seen on PCs.
So we added an "anonymous" clip where you didn't have to identify it, similar to the simplistic mechanism in Windows and other systems. After that, we never heard any customer ever refer to the multiclip mechanism.
Users of today are certainly more sophisticated wrt. tool use than those of the 1980s. Still, I would personally continue to use the simplistic Ctrl-C Ctrl-V in 98% of the cases, rather than a more functional mechanism where I would have to choose. OK, there are still 2% left, so I do see the value of a multi clipboard. In a few special cases, that is.
Didn't know the Windows-V trick, but this starts clear every time you boot the OS so it's not really a great solution. I use Ditto (https://ditto-cp.sourceforge.io/) which maintains all the history and has many excellent 'get-you-out-of-jail' features that have saved my skin so many times. Once you get used to little things like this their absence on other machines is keenly felt.
Question - when I accidentally type in the code window during debugging and VS says I have to 'edit' or 'continue', how do those options differ and why can't I EVER keep debugging instead of stopping and starting again?
I encountered that only with web applications...
I think the issue is IIS and VS try to synchronize to it...
IIS love to keep close binaries (pre-load and such), so VS have hard time to replace a DLL...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012