> No -- change your application to do it instead.

The two applications are, unfortunately, radically different.  One uses a 
proprietary 3rd party graphic environment, the other is in Java.  The one we 
want to keep keyboard focus is using that proprietary system and we don't know 
how to get it to lock the keyboard.  The guy who did the Java app (which should 
never have keyboard focus) twiddled with some Java GUI settings but the result 
was pretty bizarre behavior.  If both were written in Java (or for that matter 
any normal system) it would be a lot easier for us to control the behavior.

>> If I set the tiny GUI app (on top) to "NeverFocus" and the other one to
>> "SloppyFocus" would that work (you say it "might")?

> Yes -- providing you then focus the underlying window when you need to type
> anything --

When you say "then focus the underlying window" do you mean the user has to 
slew the pointer over (so it is no longer on the tiny app on top), or (worse) 
click anyplace on the large GUI?  Strange as this may sound, asking the user to 
make an additional click or slew is considered completely unacceptable (we are 
simulating a field system (the small GUI is a proposed new addition) and in the 
field they do not operate that way).
 
> And don't top post.

Sorry.


Reply via email to