2012/1/9 Tor Lillqvist t...@iki.fi:
I'll also try what Stephan suggested, i.e. if we can print to stdout
in Windows, too.
Note that one layer of silly wrapping could probably be dropped by
using AttachConsole(ATTACH_PARENT_PROCESS) followed by freopen()ing
stdout and stderr to CONOUT$.
If that AttachConsole(ATTACH_PARENT_PROCESS) is executed by
soffice.bin, it probably is the case that as already soffice.exe is a
gui executable, soffice.exe doesn't have a console, and thus for its
child process, soffice.bin, there is no parent process console to
attach to. Try having also
Hi Andras,
On Sat, 2012-01-07 at 23:56 +0100, Andras Timar wrote:
I've just found this feature, soffice -h displays a dialog box on
Windows with some help text.
Heh - what fun :-)
Problems:
1. Dialog is not localisable. Help text comes from const char arrays
in
2012/1/9 Michael Meeks michael.me...@suse.com:
Hi Andras,
On Sat, 2012-01-07 at 23:56 +0100, Andras Timar wrote:
I've just found this feature, soffice -h displays a dialog box on
Windows with some help text.
Heh - what fun :-)
Problems:
1. Dialog is not localisable. Help text
I'll also try what Stephan suggested, i.e. if we can print to stdout
in Windows, too.
Note that one layer of silly wrapping could probably be dropped by
using AttachConsole(ATTACH_PARENT_PROCESS) followed by freopen()ing
stdout and stderr to CONOUT$. AttachConsole() is present on XP and
later.
Hi,
Indeed, there is
helpcontent2/source/text/shared/guide/start_parameters.xhp but it is
outdated. Maybe I can update it quickly...
I'll also try what Stephan suggested, i.e. if we can print to stdout
in Windows, too.
On Windows console applications naturally print parameters to stdout.
