Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!batcomputer!munnari.oz.au!bruce!tym
From: tym@bruce.cs.monash.OZ.AU (Tim MacKenzie)
Newsgroups: comp.windows.x
Subject: Re: XWarpPointer and ICCCM....
Message-ID: <3602@bruce.cs.monash.OZ.AU>
Date: 16 Jan 91 01:53:39 GMT
References: <9101112245.AA25816@bierstadt.scd.ucar.EDU>
Organization: Monash Uni. Computer Science, Australia
Lines: 30

In <9101112245.AA25816@bierstadt.scd.ucar.EDU> morreale@bierstadt.scd.ucar.EDU (Peter Morreale) writes:
>> Section 6.2 of the ICCCM says "In general,  clients should not warp the
>> pointer".
>> 	David.
>  Allowing the user to completely fill out my template without ever
>  having to move a hand from the keyboard to the mouse is a very
>  desirable feature in my application.
>  How do people do it otherwise?

I created a sub-class of the AsciiText widget to handle this sort of stuff.
It has the extra resources XtNnext and XtNprevious which specify which widget
to transfer focus to on Tab/shift Tab. It also switches off the caret when
it does not have focus so it is apparent to the user where the focus is.

Default resources: DisplayCaret: False
Translations: <EnterWindow>: focus-in()
              <FocusIn>: display-caret(on)
	      <FocusOut>: display-caret(off)
	      Shift<Key>Tab: focus-previous()
	      <Key>Tab: focus-next()
focus-(in|next|previous) use XSetInputFocus() to set the focus to the 
appropriate widget.

I guess this could be done without creating a sub-class but it would be a
whole lot messier and cumbersome.

>-PWM
Greetings.
Tim MacKenzie
tym@bruce.cs.monash.edu.au