Command-line options on Windows don't seem to work

I need to know: does Qt on Windows use '-' or '/' as a command line argument prefix, when I did the parser for it I coded it to respond to '/' but further reading suggests that actually '-' is used.

To check: can someone start up a cmd.exe console and try running Mudlet from there with first "/widgetcount" and then "--widgetcount" and report back which one displays something like "Widgets left: 2 Max widgets: 85" on the console when the Mudlet application ends...

Neither of them show anything, but I'm also not seeing any stdout from
Mudlet as expected.

Does the code execution go as expected using '/help' '/?' or '/version' if you step through the code - is it getting to the relevant couts and those are not producing any output or is it not even getting to them there?

I haven't got gdb setup on Windows I'm afraid, that would be too much of a
pain. The command-line in general is returning right away and not showing
any of the usual stdout.

On Wed, Oct 1, 2014 at 9:30 AM, Stephen Lyons <email address hidden>
wrote:

> Does the code execution go as expected using '/help' '/?' or '/version'
> if you step through the code - is it getting to the relevant couts and
> those are not producing any output or is it not even getting to them
> there?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1375449
>
> Title:
> Command-line options on Windows don't seem to work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1375449/+subscriptions
>

Ah, right, one thought, and I do not know whether it will fly, is to: add "console" to the qmake CONFIG variable, I do not know whether this is mutually exclusive with the "windows" option ( the first indicates a windows console application and the second a GUI one) see the qmake Variables page of the documentation. Since I don't see either in the project file I wonder if the second is a default included option and the first not, but sucking and seeing might produced something...

I don't compile Mudlet under Windows so I'm afraid I can't help you with
that.

On Wed, Oct 1, 2014 at 10:10 AM, Stephen Lyons <email address hidden>
wrote:

> Ah, right, one thought, and I do not know whether it will fly, is to:
> add "console" to the qmake CONFIG variable, I do not know whether this
> is mutually exclusive with the "windows" option ( the first indicates a
> windows console application and the second a GUI one) see the qmake
> Variables page of the documentation. Since I don't see either in the
> project file I wonder if the second is a default included option and the
> first not, but sucking and seeing might produced something...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1375449
>
> Title:
> Command-line options on Windows don't seem to work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1375449/+subscriptions
>

Would Chris be able to provide some hints on my queries if we asked nicely?

Yeah.

On Thu, Oct 2, 2014 at 8:57 AM, Stephen Lyons <email address hidden>
wrote:

> Would Chris be able to provide some hints on my queries if we asked
> nicely?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1375449
>
> Title:
> Command-line options on Windows don't seem to work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mudlet/+bug/1375449/+subscriptions
>

They don't work because Windows only supports command-line XOR GUI mode - read it on SO somewhere. Closing for now, not something we can solve.