🚀 go-pugleaf

In article <1992Dec12.043729.18412@u.washington.edu> tvp@gibdo.engr.washington.edu writes:

>I'm fairly new to Windows programming. I picked up Windows SDK, VB and
.....
>
>Project 1: Take an old DOS command-line based text filter and convert
>           it to a small Windows tool.
>
>[I don't like text entry using word processors; I like input power
>through the likes of Emacs, Microemacs and now Microemacs for windows.
>The text filter I'm talking about turns whatever I've input from your
>typical text file full of hard returns, into flowable text with
>command line options of leaving blank lines between paragraphs (or
>deleting) and using one (or two) spaces after sentence ending periods.
>The source for this filter is "portable" C.]
.....
>
>to Shell() when the user hits the Run button.  It works, but I don't
>like the way the screen goes to DOS momentarily when the exe runs. I'd
>rather it just ran in the background.
>
>Question: Are there any good ways of avoiding this?
>
>Thanks in advance.
>
The thing I think I'd do is simply recompile your "portable" C filter
code using the Borland "EasyWin" library.  This will convert it into
a genuine console-style Windows application.  That way, you want get
the "flash" to DOS when the application runs.  As far as I'm aware,
there's no way to execute an genuine DOS application "invisibly".

-- 
--------------------------------------------------------------------------
| Chris Marriott                           | chris@chrism.demon.co.uk    |
| Warrington, UK                           | BIX: cmarriott              |
| (Still awaiting inspiration              | CIX: cmarriott              |
|  for a witty .sig .... )                 | CompuServe: 100113,1140     |
--------------------------------------------------------------------------