#191 Failed to register hot key 1,2,3,4

closed-works-for-me
None
5
2014-08-14
2010-09-07
No

Windows XP SP3 with latest updates

Discussion

  • This is almost certainly because another program (or Windows itself) has bound them to something else. I would need much more information to comment further, for instance you say 1,2,3,4 but these are plain keys, do you mean WIN+1, WIN+2? What is the error message? What happens when you press the hotkeys?

     
    • assigned_to: nobody --> bjasspa
     
  • Hi guys

    I attached screenshot. Previous version worked fine

     
  • The error message means that some other program has created A-C-arrow hotkeys which blocks VW from using them. There are two changes I can think of that could explain this change in behaviour:

    1) The default bindings have changed from WIN-arrow (i.e. WIN-up) to A-C-up, which did you use? If you used (and want to continue to use) WIN-up then simply redefine the bindings and it should work as before.

    2) VrituaWin's startup process changed and is a more delayed, spread out process - insignificant in human terms but required for Win7 as it creates other things like the taskbar in a different order. In theory this would allow another program to steal the bindings, i.e. you always had a conflict but in previous versions, VW won and the other program did not complain like VW does.

    So can you please look at all other software you are running and check for any that also use hotkeys (I know that some graphics drivers use these hotkeys for rotating the screen).

    The actual hotkey creation and binding process has not changed for years so it is unlikely to be an actual VW bug. BTW what versions of VW are you referring to, both the previous working one and your current one.

     
  • The error message means that some other program has created A-C-arrow hotkeys which blocks VW from using them. There are two changes I can think of that could explain this change in behaviour:

    1) The default bindings have changed from WIN-arrow (i.e. WIN-up) to A-C-up, which did you use? If you used (and want to continue to use) WIN-up then simply redefine the bindings and it should work as before.

    2) VrituaWin's startup process changed and is a more delayed, spread out process - insignificant in human terms but required for Win7 as it creates other things like the taskbar in a different order. In theory this would allow another program to steal the bindings, i.e. you always had a conflict but in previous versions, VW won and the other program did not complain like VW does.

    So can you please look at all other software you are running and check for any that also use hotkeys (I know that some graphics drivers use these hotkeys for rotating the screen).

    The actual hotkey creation and binding process has not changed for years so it is unlikely to be an actual VW bug. BTW what versions of VW are you referring to, both the previous working one and your current one.

     
  • Yes on Windows 7 alls perfect. I downloaded aproximately a year ago version and found it works great. Then I've heard that a new version came out, downloaded it and problems with hot keys began at each startup of xp or restarting the VW. However i don't do it frequently i just suspend computer at work.

    Also i wan to say VirtuaWin is the best your project and the best one among all free desktop changes i saw. Much other desktop managers hangs when you develop or debug software, or see hang up window of any application, or it takes much time to hide some window. I very appreciate support of such things, as for me they are very important. You do the great gift for all guys who use windows

     
  • From what you have said it sounds like the issue is the first suggestion, i.e. the previous version of ViruaWin was successfully registering the WIN-cursor keys and this latest version is failing to register the A-C-cursor keys.

    Do you use hotkeys to change desktop? If not simply delete them using Setup -> Hotkeys tab.

     
    • status: open --> closed-works-for-me
     
  • Closing the bug as not reproducible - I can't reproduce it and just not have any other reports of real problems in this area. I am positive this is a simple conflict with another program which can be solved by reconfiguring VW.

     
  • I just followed your advice and remove all hot keys, and everything became ok.