Comment 7 for bug 2044257

Am 21.12.23 um 15:05 schrieb djcj:
> Okay, so calling "qpdfview.exe --help" works as expected. But for some
> reason calling it with "/help" or "/?" makes it attempt to open a file
> with the name "/help" or "/?". This behavior is identical in Windows 11
> and Wine. I don't know what that's about. But it's not that important to
> have /help and /? as command line arguments, it's just common to use
> them in the Windows world.

Indeed, the parser is structured so that options always have to begin
with "--".

> Other issues I have encountered and provided a patch for:
>
> In synctex/synctex_parser_utils.c you need to explicitly call the
> PathFindFileNameA and PathFindExtensionA or else the macros
> PathFindFileName/PathFindExtension may be resolved to the wide character
> versions (which happened to me).
>
> In main.cpp you must rename "QScopedPointer< QDBusInterface >
> interface(...)" from "interface" to something else, as it will
> apparently conflict with a type/struct/etc coming from one of the
> included Windows header files.
>
> You may also want to initialize "const char* prefix" and "UINT icon"
> with an empty string and 0 to silence g++ warnings.
>
> ** Patch added: "qpdfview-1-fixes.patch"
> https://bugs.launchpad.net/qpdfview/+bug/2044257/+attachment/5731697/+files/qpdfview-1-fixes.patch
>

Please check trunk revision 2160 which should contain all of these fixes.