Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!marque!gryphon!cadovax!kaz
From: kaz@cadovax.UUCP (Kerry Zimmerman)
Newsgroups: comp.sys.amiga
Subject: Re: title bar hack
Message-ID: <1904@cadovax.UUCP>
Date: 23 Jan 88 02:23:35 GMT
Reply-To: kaz@cadovax.UUCP (KERRY ZIMMERMAN)
Organization: Contel Business Systems, Torrance, CA
Lines: 28
Keywords: window title SetWindowTitles

In article <2206@umd5.umd.edu> louie@trantor.umd.edu (Louis A. Mamakos) writes:
>One thing to keep in mind 'bout the title bar hack for the current directory
>is that not all CLI/Shells will be running in a window.  Don't forget about
>the various AUX: drivers, and maybe even a TELNET server..
>
>Perhaps if we agree that the ACTION_INFO packet should return a NULL where
>the window pointer normally is.  Then the various applications could skip
>the SetWindowTitles().
>

SetWindowTitles() may not be the correct way to change a CLI/shell window's
title.  Why? Because this routine will point the window's Title pointer
to someplace in the caller's process space.  When the calling process
exits, the Title pointer will be pointing at nothing useful.  Next time
the window needs refreshing, the nice title you had will probably be
replaced by garbage characters.

You really need do something like strcpy() the title to where the CLI's
window title is currently pointing.  I personally would not recommend
this, because we don't have the source to the CLI and don't know how
much space is reserved for its window title.  But, just using
SetWindowTitle() is not a proper solution to changing the CLI's title
bar.

Kerry Zimmerman
#  {ucbvax,decvax}!trwrb!cadovax!kaz  Contel Business Systems 213-323-8170
A difference between an amateur and a professional, 
is that a professional has the right tools.