From: jeremyd@ctc.net
Date: Mon May 13 2002 - 00:04:33 EDT
> From: Andrew Dunbar <hippietrail@yahoo.com>
> Date: 2002/05/12 Sun PM 10:05:52 EDT
> To: abiword-dev@abisource.com
> Subject: Re: commit: more Win32 cmd line processing work
>
> --- "Kenneth J.Davis" <jeremyd@computer.org> wrote: >
> CVS:
....
> > Win32 build using popt. The AbiWord source is now
> > mostly done and
> > displays in MessageBoxes, however to view the popt
> > output you still
> > need to run it through another program (e.g. Abiword
> > --help | more )
>
> I'm just wondering if message boxes are always the
> right way to show these errors on Windows.
No, but in the case of GUI applications, I believe
they probably are.
> If you're running from the command line to just
> convert files between formats without opening the GUI
> should the errors just output to the console?
That is the catch, you are opening a GUI program
[an exe marked as using the Win32 GUI subsystem]
regardless of if you use GUI components or not, so
there is no console to output to. At least, I could
not determine an API that would allow us to be attached
to the console that we were invoked from (if invoked
from a console application) without requiring another
program.
>
> Andrew Dunbar.
>
I will be more than happy to use an existing console
to output messages instead of a dialog, but someone
would have to point me to the APIs that I can use to
find and get a hold of the std file handles for that
console. This is what I originally had wanted to do,
but not determining a way to do so, I keep the existing
display method (a MessageBox), modifying to be done
within the new cmd line processing framework.
...
Jeremy Davis
jeremyd@computer.org
This archive was generated by hypermail 2.1.4 : Mon May 13 2002 - 00:07:28 EDT