开云体育

Neither a CTRL-click nor a right-click on any User-defined Controls button brings up the edit panel/window. Error log shows nothing but the following

29-Feb-2016 16:41:33 > CIVMain.ConfigCmd_Click
29-Feb-2016 16:41:33 > CIVConfig.Form_Paint

Other CTRL-click functionality okay, e.g. CTRL-Help or CTRL-n to display or edit memory notes.

Have rebooted PC and restarted Commander; have restored Commander from Launcher "Restore" with no success.

What version of Commander are you running?

When you CTRL-click a user-defined control button, does an entry for the editing window appear in the Windows task bar?

73,

Dave, AA6YQ

Commander Version 12.1.1 on Win10. Yes, there was an entry for the Edit window behind the Commander entry in the Task Bar. I clicked on the Edit entry and the Edit panel came up. Sorry for the bother. I know this is a Windows question, but how did manage to do this?

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 29, 2016 1:06 PM
To: dxlab@...
Subject: [dxlab] Re: Can't Edit Commander User-defined Controls

Commander Version 12.1.1 on Win10. Yes, there was an entry for the Edit window behind the Commander entry in the Task Bar. I clicked on the Edit entry and the Edit panel came up. Sorry for the bother. I know this is a Windows question, but how did manage to do this?

Windows supports multiple monitors. If the "Use multiple monitors" box on Commander's Configuration window is checked, then Windows can be displayed on any monitor. If your physical monitor configuration changes, or if Windows gets confused, a window can effectively be "lost", meaning displayed by a non-existent monitor. In the past, this happened with some frequency, and this procedure was provided to recover such lost windows:

<>

However, every DXLab application has been extended to detect the physical monitor configuration on startup, and automatically relocate a "lost" windows to the primary monitor. Two users subsequently reported lost "spot source" windows in SpotCollector, but that was the result of a failure to employ the "auto relocate" capability when restoring those specific windows, a defect that has been corrected. Your report of a missing window in Commander is the first such report; Commander should have automatically relocated your "lost" Edit window to your primary monitor.

If this should happen again, please do the following:

1. on the Configuration window's General tab, check the "log debugging info" box

2. terminate Commander

3. start Commander

4. on the Configuration window's General tab, ucheck the "log debugging info" box

5. attach the errorlog.txt file from your Commander folder to an email message describing what happened (e.g. identifying the "lost" window) and send it to me via

aa6yq (at) ambersoft.com

Thanks!

73,

Dave, AA6YQ