Conference bulova::decw_jan-89_to_nov-90

    >Is there an easy way to do this?
     
    Yes...but to do what you want I *think* you'll have to use DECterm EVE
    instead of DECWindows EVE.
    
    I don't have the exact syntax here, as I'm at home working on my VT320
    (chipping the letters in stone with my chisel).
    
    Under the Session Manager Customize, I'd define an application as Time
    Sheet and set the command to be something like:
    
    	CREATE/TERM/WIND=(ICON=icon_name,TITLE=title) EDIT/TPU file.ext
    
    Add this to your Applications menu and your AutoStart.
    
    For exact syntax, check the documentation.
    
    	- Dave
    

RE. 1

Thanks very much.  You were right.  That was an easy way to get the title I 
wanted in the right places.

However, I am still running into a problem.  Let me explain.  Once the window
is created I want to run a command stream.  Within this command stream I do
some prelimanary stuff before executing the EDIT/TPU command.  The command
stream seems to be source of problem.  When I execute this window creation
through Application Menu pull down the window appears for a couple of seconds.
It then dissappears off of screen.  Process is gone.  When I execute the same
command from an already existing DECTERM window at the DCL prompt it works fine.
Creates window and executes command stream successfully.

I have built a small command stream that simply types out file.

	DECWTEST.COM

		$ TYPE SYS$LOGIN.LOGIN.COM

My application definition is;

CREATE/TERM=DECTERM/DISPLAY=KAM102::0/WINDOW_ATTR=(TITLE="TEST",ICON="TEST")
 @DSK15:[DIRECTORY]DECWTEST.COM

When I try and execute this com stream nothing happens.  Window appears for
couple of seconds and then goes away.

What could be causing this?  Does it have anything to do with where 
SYS$INPUT is pointing or SYS$OUTPUT.  This leads to me to one more question.
When DECWindows opens up window does it execute the DECWindows login command
file located in my SYS$LOGIN directory before doing anything or does it 
execute the command stream in my CREATE/TERM command first?

While writing this note a thought came to mind.  I tried the above CREATE/TERM
command without executing the COM stream.  The window came up, I saw the DCL 
dollar sign($) and then window vanished. 

Now I am totally confused and would appreciate help on this.

Thanks in advance...Bruce

    Try adding /DETACH to the application definition.  I think you're
    creating a subprocess to execute the @DECWTEST command, and it
    goes away when the process executing the CREATE/TERM completes.
    
    Tim

    When you execute the CREATE/TERM command, a subprocess is spawned
    unless you specify the switch /DETACH.  If spawned, then the existing
    symbols and logicals are copied and the LOGIN.COM file is NOT executed. 
    If /DETACH is specified, then LOGIN.COM *IS* executed.
    
    When DECterm is executed with a command line, like:
    
    			CREATE /TERM type foo.bar
    
    after the command completes, the DECterm goes away.  Just place your
    edit command as the last line in the command file.  Have the command
    file loop if need be to keep the DECterm alive.
    
    I tried your command exactly as is on an OOTB IFT system, and it worked
    fine.  It even works with the EDIT command.  Is there anything else
    different about what you're trying to do?
    
    Jim
    

    To change the Icon label of a DECwindows TPU application, use the 
    
            SET (ICON_NAME, string) 
    
    built-in function.  SET (ICON_NAME, "Time Sheet") will change the icon
    to say Time Sheet.  (This code would be saved in a time_sheet.tpu file
    or in a private section file).
    
    To change the Text in the menubar, modify 
    Decw$user_defaults:time_sheet.dat to have the line:
    
            Tpu.Tpu$MainWindow.Title:		Time Sheet
    
    Then define an application in the session manager to do:
            
        edit/tpu/inter=decw/command=time_sheet.tpu
            /defaults=time_sheet time_sheet.file
    
    This many be a bit more complicated that the create/term but it gives
    you all the advantages of DECwindows EVE.
    
                                August G. Reinig

August,

Thank you for your suggestion. You mention that your suggestion is not quite 
as easy but I have been trying the other route using the CREATE/TERM and have
not been successful.

You have to bear with me because I do not have a lot of experience working with
.TPU and section files.  I have made an attempt but I still no success.

Let me explain what I did and maybe you can tell me what I am doing wrong.

I invoked the editor with the following command;

$ EDIT/TPU/DISPLAY=DECWINDOWS/SECTION=MYEVE

where MYEVE is a section file I already have.

When in EVE I typed into the current buffer following

decw_icon_name := "BW-Weekly Status";
SET (ICON_NAME,decw_icon_name);
SAVE ("work:bw_weekly_status");
quit;

Then at the Vaxtpu prompt, I type EXECUTE (CURRENT_BUFFER);

When it does this execute, I get a compilation error of the following

"Feature requires the VAXTPU DECwindows screen updater"

The reason I want to save above is so that the current definitions that I 
have in my EVE application will get saved to this new section file with
this ICON set.

As to your suggestion of creating the .DAT fiel, I simply created it using
editor.  Is this correct?

I hope I have not been too long winded on this but I have been trying to this
for a couple of weeks now and have not had much success.  If you can help
I would be grateful.

Thanking in advance...Bruce

    1. The ICON_NAME does not get saved in a section file.  You will have
    to execute the SET (ICON_NAME) built-in each time you bring up EVE. 
    The call to this built-in should be in your section file initialization
    code.  You may want to protect it with:
    
            if get_info (SCREEN, "decwindows") 
            then
                SET (ICON_NAME, "BW-Weekly Status")
            endif;
    
    2. I don't know why you got the "Feature requires..." message unless
    you weren't running DECwindows TPU.
    
    3. Creating the .DAT file via an editor is correct.
    
                                August

Re-reading a few of these it sounds like you are running EVE from a DECTERM and
not EVE's DECwindows interface.  Do you know such a thing exists?  You don't
have to create a DECTERM to start up eve, have your session manager
application defintion do a:

edit/tpu/interface=decwindows/section=myeve .........

Otherwise you would have to do a:

create/term/window_attributes=(icon_name="{icon-name} ", title="{whatever} ") edit/tpu/section=myeve filename

which will create a decterm running character cell TPU with your section file.
With this setup you can not use EVE or TPU commands to change the window title
or icon title.


Brian J. McCarthy

Re; .8

August,

I have done what you indicated in .6 and .8 and still no success.

To begin I created an init .TPU file named BW_WEEKLY_STATUS.TPU
like the following

PROCEDURE tpu$local_init

SET (ICON_NAME,"BW-Weekly Status");

ENDPROCEDURE;

Using the above I did the following to add to my current EVE section file.

$ EDIT/TPU/DISPLAY=DECWINDOWS/SECTION=WORK:DECW_MYEVE/-
  COMMAND=BW_WEEKLY_STATUS.TPU

I then defined an application definition in the session manager like the
following;

edit/tpu/display=decwindows/section=work:decw_myeve/-
defaults=bw_weekly_status file_to_edit

	where the defaults file (BW_WEEKLY_STATUS) is a .DAT file that 
	exists in my SYS$LOGIN directory. It only contains the title command
	you gave me from note .6

When I invoke this the window comes up and it is editing the correct file.
However, the TITLE is not in the window nor is the ICON_NAME what I specified.
The ICON_NAME is "VAXTPU" and the window TITLE NAME is "DECWindows VAXTPU".

And EVE displays the following error message

Don't understand initialization command: SET (ICON_NAME,"BW_WEEKLY_STATUS")

I cannot find this command in the help for EVE either.

Once again your help would be appreciated.

Thanking in advance again...Bruce
 

For those who are interested in what has become of all this

Referring to .6 I created the .DAT file containing the title
command.  Word of caution.  When creating pay close attention to the
case.  This can cause problems if not exactly same as in .6.

I created a .TPU file containing the one line

	SET (ICON_NAME,"BW-Weekly Status")

I then used the following command in the application definition portion
of the session manager.

edit/tpu/display=decwindows/command=file.tpu/defaults=file.dat file_to_edit.ext

Not sure if someone out there would like to do this but if so this was my
solution.

Thanks to all that gave help.

Bruce