Some senseless babbling from Jonathan De Boyne Pollard to Mike Ruskai
on 19 Nov 98  09:40:16 about full screen ??...

 JDBP>> Actually, the more widely accepted terminology (i.e. everything
 JDBP>> other than the IDE for Borland C++ for OS/2 (-:) is "Not Window
 JDBP>> Compatible", "Window Compatible", and "PM".

 JDBP>> Or, alternatively, "FULLSCREEN",
"PMCOMPATIBLE", and "PM".
 
 MR> VACPP calls the types None (program determines itself what mode to run
 MR> in),  Window (VIO), PM, or Full Screen.

 JDBP> Then VAC++ is mistaken.  If the type is "None", it is the *parent
 JDBP> process* that determines what mode to run in, via parameters to
 JDBP> DosExecPgm or DosStartSession, rather than the program that is being
 JDBP> executed. 
 JDBP> After all, by the time that the program has started execution, the
 JDBP> session that it is running in has already been determined.

That doesn't make any sense, Jonathan.

DosExecPgm has no parameters which would indicate the type of process being 
started.  DosStartSession is clearly intended for a process to start its 
own window session.

The program itself is what determines how it runs.  

Using the option entitle "None" with VACPP allows one to write an 
application that runs as a Presentation Manager program, VIO program, or 
Full Screen program based on runtime information.  Most likely, a 
command-line switch.

Mike Ruskai
thanny{at}home.com


... Excuse me, miss?  Miss!?  Sorry, I have a cold.
--- Renegade v05-11 Exp