Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!converse
From: converse@EXPO.LCS.MIT.EDU (Donna Converse)
Newsgroups: comp.windows.x
Subject: Re: Executing X11 programs
Message-ID: <8906221538.AA08218@expo.lcs.mit.edu>
Date: 22 Jun 89 15:38:32 GMT
References: <4161@uhccux.uhcc.hawaii.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 35


> For executing any program,
> I am not sure whether 'uwm','xterm' should be running at background mode
> or not.

You should have a window manager, such as uwm, running in the background.

> But even if they are running in background and if I execute my
> program, the response is ...  nothing will be displayed on the terminal
> (in the window).

It sounds as though your program will open a new window on the screen
and write your name in that new window.  If no new window appears, or
if a new window appears but nothing is written in it, then there is
some other problem with your program.  

> But before mapping a window, standard properties
> are to be set using XSetStandardProperties(.......) function (of Xlib).
> This function has Argc & Argv as two of the arguments to be passed/specified.
> These arguments are to be passed while executing the program (i.e command
> line arguments). But I do not know the arguments to be specified, the syntax
> /format of the arguments.

Don't worry about this; whatever arguments there are to your application,
if any, just pass them in.   Just pass in argv and argc as your program
received them from the command line.  It will be used to set the 
WM_COMMAND property.  The window manager will communicate this information
to the session manager, which uses this and other information to re-start
your programs at the point where you last stopped working, for example,
to allow to pick up work where you last left off, between login sessions.
Your X software may not have a session manager.


Donna Converse
converse@expo.lcs.mit.edu