Alexandre, Keyboard focus is an important concept, and Polymorph (or in general the window manager currently in use) needs to manage it. How about this: teach OB that control-t means run tests, and wash it through the normal hierarchy of keyboard handling - the mouse location is irrelevant at this stage. The control-t arrives where keyboard input goes: to the view with focus. There is an accepted way to do the next part: I _think_ it involves checking for a matching shortcut, but I honestly do not remember. Gary will know, or will find out within minutes. Failing that, I can consult my copy of the Borland Open Architecture Guide for its documentation on Object Windows; that gives an idea of how long these things have been done a certain way. IIRC, once identified as a shortcut, it walks up the view/command hierarchy until something knows what to do with it - in this case, OB would look for a selection in the relevant pane, and run tests.
If you have no selection, then you will end up clicking and changing focus that way, which is fine. The approach outlined above should provide the behavior you want w/o distributing GUI management into individual tools. In fact, there is nothing to stop this code from using the current mouse location to find the "item under the cursor" and run tests on it. I would rather it not do that, but go for it if that's what you want. The point is that you do not need to work against Polymorph's focus management to get the behavior. Re anything you might be missing, consider me on a good typing day. People have been known to complain about the racket. There are faster typists, but I can do a pretty good test. I type words, not characters (I have to slow down to do the latter). If focus is grabbed "at random" because I bumped the mouse with my elbow (I've even seen cursors drift with no apparent motion of the mouse), a change of focus will result in (just guessing) three to five characters being sent to a list that will start trying to make selection to match characters before I can begin to react to it. Does that make sense? Bill ---- Wilhelm K. Schwab, Ph.D. bschwab AT anest DOT ufl DOT edu ________________________________________ From: [email protected] [[email protected]] On Behalf Of Alexandre Bergel [[email protected]] Sent: Friday, February 20, 2009 9:11 AM To: [email protected] Subject: Re: [Pharo-project] Automatic focus on column upon moose enter I do not know what is mouseClickForKeyboardFocus I just feel that when putting the moose over a column, in which an item is selected, and pressing a shortcut for a command should execute the OB command. Am I missing something obvious? Cheers, Alexandre On 20 Feb 2009, at 15:05, Gary Chambers wrote: > I've asked David if he would preference it... > > As for the mouse wheel, that does follow the mouse pointer so I was > confused > as to why anyone would want the keyboard focus to follow the mouse > for OB > columns irrespective of the mouseClickForKeyboardFocus preference. > Each to > their own (hence preference required). > > Regards, Gary > > ----- Original Message ----- > From: "Schwab,Wilhelm K" <[email protected]> > To: <[email protected]> > Sent: Friday, February 20, 2009 1:38 PM > Subject: Re: [Pharo-project] Automatic focus on column upon moose > enter > > >> Alexandre, >> >> Can you give us an explanation or pointer to one? This sounds like >> something that Gary worked hard to stop from happening. I want you >> to >> have what you want from your image, and I need my future users to >> have >> what they will demand (loudly<g>). I am also convinced that there >> are >> things (e.g. mouse wheel input) that should "follow the mouse" >> without >> affecting keyboard focus, and this might be one of them, but >> referring to >> focus gives me the idea that keyboard input will go to the columns >> based >> on mouse position, and that (PLEASE!!!!!) needs to be optional - it >> drives >> me batty. I type quite fast, and if the input goes to what amount to >> commands instead of editing, it can get ugly. >> >> There are some preferences that control behavior like this, and any >> such >> overrides should be conditional on one being set, or moved into the >> themes, probably as an aspect vs. implied by the theme choice. By >> the >> latter, I am assuming that you want Motif style mouse/focus >> behavior in >> any old theme you happen to choose. That's fine, but it should be >> optional or we are taking a step backward in feel. >> >> Bill >> >> >> ---- >> Wilhelm K. Schwab, Ph.D. >> bschwab AT anest DOT ufl DOT edu >> >> ________________________________________ >> From: [email protected] >> [[email protected]] On Behalf Of Alexandre >> Bergel [[email protected]] >> Sent: Friday, February 20, 2009 5:04 AM >> To: Pharo Development >> Subject: [Pharo-project] Automatic focus on column upon moose enter >> >> David, >> You're a hero! >> Thanks for OB-Enhancements-dr.305 >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
