Re: [Scid-users] F2 shortcut for engine analysis

2008-07-24 Thread Michal Rudolf
Pascal Georges, czwartek, 24 lipca 2008: >If the engine window is minimized and the user thinks it is not opened, >pressing F2 twice will bring the analysis window up. If F2 starts/stops the >engine, the window has first to be made visible, then the engine states >changes ... Seems complicated to

Re: [Scid-users] F2 shortcut for engine analysis

2008-07-24 Thread Pascal Georges
2008/7/24 Michal Rudolf <[EMAIL PROTECTED]>: > Pascal Georges, czwartek, 24 lipca 2008: > > >This would mean F2 is a tristate command, which should be avoided. I'd > >prefer another global shortcut (currently "a" toggles annotation but as it > >collides with entering moves with keyboard, it canno

Re: [Scid-users] F2 shortcut for engine analysis

2008-07-24 Thread Michal Rudolf
Pascal Georges, czwartek, 24 lipca 2008: >This would mean F2 is a tristate command, which should be avoided. I'd >prefer another global shortcut (currently "a" toggles annotation but as it >collides with entering moves with keyboard, it cannot be generalized). Not really tristate, it will mean: s

Re: [Scid-users] F2 shortcut for engine analysis

2008-07-24 Thread Pascal Georges
2008/7/24 Michal Rudolf <[EMAIL PROTECTED]>: > Often, when pressing F2 with analysis engine window open, I get following > error: > > invalid command name ".analysisWin1.b1.multipv" > invalid command name ".analysisWin1.b1.multipv" >while executing > "$w.b1.multipv configure -from $min -to $ma

[Scid-users] F2 shortcut for engine analysis

2008-07-24 Thread Michal Rudolf
Often, when pressing F2 with analysis engine window open, I get following error: invalid command name ".analysisWin1.b1.multipv" invalid command name ".analysisWin1.b1.multipv" while executing "$w.b1.multipv configure -from $min -to $max -state readonly" (procedure "makeAnalysisWin" line