Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
Is there a callable DECterm which you can fire up a DECterm widnow and pass and run a DCL command procedure? User need be able to click any window and work on it including the newly created DECterm window. Thanks.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3220.1 | decwtermport | TOOLEY::B_WACKER | Fri Aug 17 1990 15:19 | 3 | |
decw$termport see 5.1,.2,.3 release notes. Bruce | |||||
3220.2 | Another way | SCAM::DIAL | Mon Aug 20 1990 10:41 | 4 | |
You can also spawn a subprocess that does a create/terminal/process. I've used both methods, and find the spawn easier. Barry | |||||
3220.3 | how to manipulate the DECterm | HSOMAI::HO | Tue Aug 21 1990 17:05 | 3 | |
Is the DECterm created by DECwTermPort a widget. If it is, how do I obtain its widget ID or window ID so that I can user Xlib routines to give it input focus or raise it to the top? | |||||
3220.4 | It's possible, but not recommended. | SCAM::DIAL | Mon Aug 27 1990 10:18 | 12 | |
DECterm uses widgets, but they are not owned by the program that calls DECwTermPort. Getting the window ID for manipulating focus, or raising the the window is possible, but only through real ugly hacks that are subject to breaking. Not only that, but assigning input focus for another application breaks the decwindows rules. We all know that rules are made to be broken though, don't we? In the past, there has been a lot of discussion about this in the DECTERM notes file. I can't provide a pointer, because it seems to have moved since the last time I looked at it. That said, the program I used as a model for doing this was CYCLE which is disussed in the DW_EXAMPLES notes file. Barry |