> I think what Eike suggests is to use guistdio.exe (perhaps rename it
> appropriately, to something like soffice.com), and use _that_ when
> calling soffice from the command line.
>
If I recall correctly from when I a long time ago had a look, Windows
nowadays (well, since XP at least) has APIs t
Kaganski Mike wrote:
> Unfortunately, the solution in the guistdio.inc is to make the
> application a console application (having SUBSYSTEM=CONSOLE [1]) by
> providing main instead of WinMain. This has the drawback of flashing
> console that is always created by OS when launching such programs,
> a
11/23/2016 3:45 PM, Eike Rathke пишет:
Back in old times there was a guistdio.com built for Windows that when
copied to soffice.com somehow attached stdout to the console and invoked
soffice.exe
No idea if that is still functional, but the source is in
desktop/win32/source/guistdio/
Thanks for y
Hi Kaganski,
On Tuesday, 2016-11-22 20:42:01 +, Kaganski Mike wrote:
> Could you please share your thoughts on this? Did I miss some way to
> implement it better?
Back in old times there was a guistdio.com built for Windows that when
copied to soffice.com somehow attached stdout to the con
Hello,
Currently, under Windows the command-line help information (that is available
using soffice --help) and version information (soffice --version) are shown in
a dedicated dialog window (CmdlineHelpDialog). That has following problems:
1. The dialog does not allow for scrolling, resizing an
