|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Sat Apr 05, 2008 3:01 am
[2.21] Ctrl-Q not working for me except in a blank session |
If I load a blank session I can type ctrl-q and it does the speed testing. It doesn't work in my current session.
I've both imported my session back into a clean session from xml and I clean installed Cmud, copying back my package afterwards.
Any ideas on what might be causing this? |
|
|
|
Larkin Wizard
Joined: 25 Mar 2003 Posts: 1113 Location: USA
|
Posted: Sat Apr 05, 2008 11:46 am |
Confirmed. It doesn't work on my session now, either.
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sat Apr 05, 2008 4:41 pm |
Works fine for me here in a blank session. If it doesn't work within your session, make sure you don't have a macro assigned to CTRL-Q or something like that. Not sure what could cause it not to work. You might also try using the
#CMD speedtest
to see if that works to determine if it's a problem with the CTRL-Q shortcut or the command itself. |
|
|
|
Arminas Wizard
Joined: 11 Jul 2002 Posts: 1265 Location: USA
|
Posted: Sat Apr 05, 2008 4:46 pm CTRL-Q |
It worked here from both CMUD and CMUDPro in Untitled and my Achaea session.
|
|
_________________ Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
|
JQuilici Adept
Joined: 21 Sep 2005 Posts: 250 Location: Austin, TX
|
Posted: Sat Apr 05, 2008 5:04 pm |
Does your session have the mapper open? Ctrl-Q causes the mapper to re-center on the selected room, and it's easy to miss.
|
|
_________________ Come visit Mozart Mud...and tell an imm that Aerith sent you! |
|
|
|
Arminas Wizard
Joined: 11 Jul 2002 Posts: 1265 Location: USA
|
Posted: Sat Apr 05, 2008 5:19 pm |
Ok, I went and found my ancient Avalon session and tried it there.
At first it did NOT work. When I came back to post about it I read JQuilici's comment and checked.
The difference between when it worked for me and when it did NOT work was that in the session that worked the mapper was open but not docked.
If the mapper is closed or open and undocked it works. If the mapper is docked then Ctrl-Q isn't working. |
|
_________________ Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
|
shalimar GURU
Joined: 04 Aug 2002 Posts: 4662 Location: Pensacola, FL, USA
|
Posted: Sat Apr 05, 2008 6:17 pm |
I was having this issue too, but it was just my map being open.
P.S. Aren't mapper shortcuts currently NOT supposed to work when the mapper is docked? |
|
_________________ Discord: Shalimarwildcat |
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Sat Apr 05, 2008 11:28 pm |
Yeah, it was the mapper for me. Both undocking the mapper and using #cmd speedtest worked for me.
I'm guessing this is already on the long list of mapper rewrite items. |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Apr 07, 2008 5:16 pm |
Actually, this sounds more like a problem with the menu shortcuts in the docked windows interferring with each other. It's very possible that this is a problem I fixed in older versions by modifying the DevExpress source code, and that this "fix" got lost when I upgraded the DevExpress menu/toolbar components. Although I didn't change anything in 2.22 that should have caused this, so I would have thought the same problem would have existed in the 2.20 and 2.21 versions too.
In any case, I have put this onto the bug list. |
|
|
|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Wed Feb 04, 2009 3:40 pm |
Is this the type of mapper bug fix that belongs in stage 2?
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Thu Feb 05, 2009 5:52 pm |
Not really any specific phase...it's a generic problem with having a single window with multiple docked sub-windows with multiple menu bars. Windows is not designed to handle multiple menu bars within a single window, so the components that are used to dock windows with menu bars try to trick Windows into executing the menu shortcuts from the correct menu, and sometimes this fails.
It's not specific to the mapper...if I allowed the Settings Editor to be docked (or any other window with a menu), then you'd see similar problems.
Solving this problem is very tricky and involves working with the source code of the 3rd party docking and menu/toolbar components. So because this particular problem is difficult to solve correctly, and the problem itself is pretty minor, it gets a very low priority in my bug list. |
|
|
|
|
|