| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 784.1 | | 32148::KLEINSORGE | Toys 'R' Us | Tue May 16 1989 13:05 | 7 |
|
I think that the terminal architect indicated that the workstation
terminal emulators *not* recognize that sequence as it's intention
was not so broad.
|
| 784.2 | | 7130::LOMICKAJ | Jeff Lomicka | Tue May 16 1989 13:10 | 13 |
| Nowithstanding the lack of architecture in this area, my statement still
stands that DECWindows is ENFORCING the policy of not allowing
application to assign input focus to the emulators that they themselves
create.
Well, okay, VWSLAT should really be using the DECTerm widget directly
instead of the DECW$TERM_PORT, at which point VWSLAT would have the
control it needs - but bear in mind that DECW$TERM_PORT is currently
the only supported way to create DECTerms. If I use the DECTerm widget
in VWSLAT, I could run into trouble with the "undocumted interface"
barrier to entry into ASSETS.
|
| 784.3 | | 32148::KLEINSORGE | Toys 'R' Us | Tue May 16 1989 13:20 | 15 |
|
How is the enforcement done? As this is an internal product and at
"best" may someday become a ASSET application (i.e. "as is" ), are
there not ways of doing this in complete disregard of any standard
(especially sine the "standard" may be obviated by a new "standard"
(Motif) soon)?
Strict conformance to such a rule when it is *clearly* the intention
of the user to create and use a new window is crazy. It's like when
the default for TPU was to pop up a EVE window, leave the terminal
window useless (as it was running TPU) and yet not even switch the
input focus to the EVE window.
|
| 784.4 | | 7130::LOMICKAJ | Jeff Lomicka | Tue May 16 1989 13:28 | 7 |
| The "enforcement" is that no mechanism is provided for assigning the
input focus to the window. There's no OSC or CSI sequence, and no
reliable or even acceptable way of getting the window ID, and as far as
I know, no set-up file or customization string entry I could provide in
order to get it to take focus upon creation.
|
| 784.5 | | 4268::RASPUZZI | Michael Raspuzzi - VMS/LAT Engineering | Tue May 16 1989 13:50 | 6 |
| One could add "grab input focus" when a new window is created in the
customize procedure. This could be off by default and if a user wants
input focus on newly created windows, they could enable this.
Mike
|
| 784.6 | How do I do this? | 20935::SHEPRO | Service Before Protocol | Tue May 16 1989 15:46 | 5 |
| The content of the replies to my original question/concern is beyond me. In
response to .5, though, How do I do this?
Alan
|
| 784.7 | | 4268::RASPUZZI | Michael Raspuzzi - VMS/LAT Engineering | Tue May 16 1989 16:22 | 17 |
| Re .6:
You can't do it. I was speaking from a programmers point of view. For
example, let's say I am enhancing DECTerm. One item I might want to add
in the customize settings window is something like "Grab input focus when
new window is created". A user would go to customize on the menu bar
of a DECTerm, select change settings and in the window that pops might
one of the items that could be selected would be "grab input focus..."
The wording in my original message does lead one to believe that it can
be done today but it can't. I'm merely suggesting that applications
that create windows (like DECTerm) that might want to grab input focus
(or might not want to grab input focus) could have a customize setting
that would allow a user to set it to his or her liking.
Mike
|