JdBP> To be honest, I don't see any reason for keeping this check in
 JdBP> PM, and I wish that IBM would remove it.  It's a kludge that
 JdBP> tries to create, with smoke and mirrors, the effect that there
 JdBP> are different "types" of sessions when in fact there aren't. 
 JdBP> OS/2 Warp would be much more useful *without* this kludge,
 JdBP> because programs could then use a combination of PM and
 JdBP> text-mode if they wanted to. 

They can!

The only thing a programmer has to do is to

- write a multithreaded VIO program
- link with a PM DLL

then if he would any PM ineraction he starts a thread that calls the DLL and
this can interact with PM as it likes. It is a little bit tricky but works
well.

 JdBP> If Presentation Manager didn't have this check in it, PMCMD
 JdBP> would actually be able to display graphical windows as normal,
 JdBP> *as well as* be able to print messages to its standard output
 JdBP> and have them displayed on the session's console.  There
 JdBP> wouldn't be this artificial distinction between "text mode
 JdBP> programs" and "graphical programs". There would just be
 JdBP> programs, which could choose to use the session's console to
 JdBP> display a textual user interface or choose to use the
 JdBP> Presentation Manager graphics library to display a graphical
 JdBP> windowing user interface, or even choose to do both.

It is a problem of PM (pmshell.exe) to hold full control over screen, mouse,
keyboard not of OS/2.



--- Sqed/32 1.15/development  27: