From: Masatsugu Nagata (nagata@kurims.kyoto-u.ac.jp)
Date: 14 Mar 01, 02:21 EST
From: Masatsugu Nagata <nagata@kurims.kyoto-u.ac.jp>
Subject: Feature-Request: Please separate chooseWindowStatus and chooseWindowList
Vince, I have another feature request, regarding chooseAWindow.
Currently, chooseWindowStatus which is equal to chooseAWindow depends
on the state of the 'useStatusBar' flag, and behaves differently
(uses StatusWin prompt if useStatusBar is 1 and uses listpick dialog if
useStatusBar is 0.)
That means, ONLY ONE of the two different procs is available for one user.
I think this is not the right thing to do. In my personal usage, I use
chooseWindow-via-status-prompt extremely frequently, but I ALSO use
chooseWindow-via-listpick-dialog, quite rarely, but certainly do.
chooseWindow-via-status-prompt is an extremely fast way to switch windows,
so it's for use as the main way to switch windows. But when there are
many windows open, especially with similar names, it's not the ideal
method. In such cases, window name selection via the listpick dialog
is more convenient, more accurate and faster.
I know, we can also use the Window Menu, but menus are awkward when there
are many items, and also I have to move my hand away from my keyboard
to reach the mouse, which needs more attention, taking away my
concentration on the current subject.
So, my point is that it is necessary to have BOTH of the two chooseWindow
procs available (each bound to different keystrokes, I bind them to
Help and control-shift-Help, respectively, in my setup...
I would recommend command-";" and command-option-";", perhaps, for the
general distribution.)
How about replacing the following line in 'BackCompatibility.tcl'
(line 29 of BackCompatibility.tcl)
proc chooseWindowStatus {} { chooseAWindow }
with the following:
proc chooseWindowStatus {} {
global useStatusBar
set temp $useStatusBar
set useStatusBar 1
chooseAWindow
set useStatusBar $temp
}
proc chooseWindowList {} {
global useStatusBar
set temp $useStatusBar
set useStatusBar 0
chooseAWindow
set useStatusBar $temp
}
I absolutely do not doubt Vince's good intention, but it is certainly
heart-breaking to see my own hand-crafted procs being replaced by
half-cooked procs that fail to work properly in the everyday usage...
;-)
Mark
--
Mark Nagata
mailto:nagata@kurims.kyoto-u.ac.jp
_______________________________________________
AlphaTcl-developers mailing list
AlphaTcl-developers@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/alphatcl-developers