A few days ago I suddenly couldn't use the Ctrl+C hotkey combo to copy text in programs like firefox, notepad or Dopus any more. Or in any other program. I also discovered I couldn't use Ctrl + A, or Ctrl + V, etc. I can however use those hotkeys to copy/paste files, only selecting and copying text is a problem. When I select text and use Ctrl+C (in for example firefox) some file gets copied on the background in Dopus instead of the selected text.
It took 2 days of searching and LOTS of frustration before I discovered my recent upgrade to Dopus 10 was responsible for this really annoying mess. Since then I learned about configuring hotkeys, unchecking the checkboxes for systemwide hotkeys like Ctrl+. This more or less helps; I can get the keys to the way I want like it used to be in Dopus 9. Like regular behaviour as I used to know for years in lots of Windows programs...
Problem though is that this is only a temporarily solution, after a restart the boxes are checked again.
I don't understand how I can get this the way it used to work. I also don't understand why all this is necessary. I really do hope somebody is able to help me and maybe even explain to me what is the use of al this?
For the moment I really regret having spent money on upgrading to Dopus 10, even though I can see some other things have improved... It shouldn't be necessary spending this much time and frustration for something this basic, that should be working without questions.
There are no system-wide hotkeys defined by default in Opus that use the Ctrl key. Check that you haven't floated a toolbar that has them in it, as hotkeys assigned to floating toolbars are global by default.
Specifically... it sounds like you yourself must have changed something related to the new "Menu" toolbar that holds the File, Edit, Tools, and Settings menu items. The <Ctrl+C> hotkey is on the copy item under the Edit menu. For instance, if you've set the Menu toolbar as a floating toolbar like Jon suggested, the <Ctrl+C> hotkey will then become global and behave as you described...
That said... it doesn't sound to me like you have that toolbar set to floating... if you float that toolbar, the hotkey entry in the Customize dialog certainly will then say "Yes" in the Global column... but you can't edit that hotkey and "disable" the system wide hotkey checkbox... at least, this checkbox isn't available when editing the hotkey in this state on my system. I think that's because Opus realizes it's a hoteky assigned to a toolbar and calls up the regular command editor for toolbar buttons - which doesn't seem to include a "System-wide Hotkey" checkbox like regular hotkey definition (not associated with toolbar buttons) command editor dialogs have...
Anyhow - I only mention this because you said you temporarily "fix" it by disabling the "System-wide Hotkey"... and I don't see how you'd be doing that if you had set one of those toolbars to 'floating'.
You're right - you sohuldn't have to struggle with this and I bet it's frustrating... but this isn't "normal" behavior for Opus. There has to be something you've done that unkowingly triggers this behavior. I'd say there's also something ELSE wrong in that "however" your system enabled system-wide flag for those hotkeys... once you "disabled" it - it should have stuck and not RE-ENABLED the system-wide flag. That usually sounds like some kind of weird permissions issue with Opus not being able to save it's config file changes based on your change to the hotkey setting. Dunno... if you don't have anything "sensitive" like passwords and and folders you don't want others to know about - maybe you could PM somebody your Opus config (Settings->Backup and Restore)... and someone could reproduce and puzzle out what's up with your config for you...
Thanks for your fast replies.
I have never used floating toolbars, not in Dopus 10 and also not in 9. This strange behaviour occurred after upgrading to Dopus 10. I reinstalled Windows 7 (for other reasons) a day later, and installed Dopus 10 again. I then found the problem was gone, but it was there again after I "installed" my earlier backed up Dopus config (like I did before). This was a backup made while using Dopus 9, so I guess something went wrong there? The backup I used was flawless when I used it in Dopus 9 though. I just assumed I could use the same config in the new Dopus version. A lesson learned...
Anyway, the problem has been solved now, so I am relieved and a lot happier.