[Flightgear-devel] Launcher - does not process additional settings textbox data

[Ron H]

Hi,


I cannot get the launcher to process the following in additional settings:


--generic=socket,in,25,localhost,5550,udp,headtracker --generic=socket,out,10,localhost,5551,udp,headtracker --config="E:/projects/fgmeta/data/Nasal/headtracker.xml" --prop:browser=/sim/headtracker


This additional setting text is used to start FaceTrackerNoIR - it works as a command line parameter, but will not work in the launcher additional settings textbox text.


FG as a short cut with the following works:


"F:\Program Files\FlightGear 2017.3.0\bin\fgfs.exe" --generic=socket,in,25,localhost,5550,udp,headtracker --generic=socket,out,10,localhost,5551,udp,headtracker --config="E:/projects/fgmeta/data/Nasal/headtracker.xml" --prop:browser=/sim/headtracker


I was trying to debug fglauncher, but seems QT has issues trying to debug in windows.


Ron


Windows 10, VS2015

[James Turner]

> On 23 Jul 2017, at 21:30, Ron H <***@hotmail.com> wrote:
>
> I cannot get the launcher to process the following in additional settings:
>
> --generic=socket,in,25,localhost,5550,udp,headtracker --generic=socket,out,10,localhost,5551,udp,headtracker --config="E:/projects/fgmeta/data/Nasal/headtracker.xml" --prop:browser=/sim/headtracker
>
> This additional setting text is used to start FaceTrackerNoIR - it works as a command line parameter, but will not work in the launcher additional settings textbox text.
>
> FG as a short cut with the following works:
>
> "F:\Program Files\FlightGear 2017.3.0\bin\fgfs.exe" --generic=socket,in,25,localhost,5550,udp,headtracker --generic=socket,out,10,localhost,5551,udp,headtracker --config="E:/projects/fgmeta/data/Nasal/headtracker.xml" --prop:browser=/sim/headtracker

To be clear is it only the ‘config’ option which fails? I am guessing it’s the embedded quotation marks which break it? Or do the generic options also have problems?

>
> I was trying to debug fglauncher, but seems QT has issues trying to debug in windows.
>

What problems? debugging Qt on Windows ‘just works’, I do it most days (that I’m working on Windows)

Kind regards,
James

[Ron H]

James,


It seems that the -config is not executed - I do get a window displaying the sim/headtracker properties. I assume the socket part works as I see the headtracker properties change in the property browser window. I always put quotes around folder path names assuming that spaces in names causes issues. Not at my machine currently will test later - Added the full path as I do not have FG_ROOT set in my system. Looking at the command line page in the launcher shows all the command line parameters and --config has been striped of the quotes. I would have assumed that the same format would work in both command line execution and --launcher execution.


As to QT. I assumed debugging with QT should work and there is something wrong with my setup. I always seem to get a break just as the sections in settings are being processed. - again not at my machine currently. The debugger asks for qqmlcomponents.cpp - I don't have that file in my set-up. Overall, I am set-up similar to Jenkins. I have downloaded qt 5.6.1 single archive for x64.


I have built/compiled OSG 3.5 debug, simgear debug and flighgear debug. QT is in a separate folder on the same drive. Debugging from VS2015. Any suggestions as to a better/different folder structure or debug environment would be appreciated. Debugging FG w/o --Launcher seems to work.


I have not created a QT id, just downloaded the installer for QT 5.6.1. Are there additional files needed to debug QT?


Thanks

Ron


Windows 10, VS2015


________________________________

Sent: July 24, 2017 5:01 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Launcher - does not process additional settings textbox data


On 23 Jul 2017, at 21:30, Ron H wrote:

I cannot get the launcher to process the following in additional settings:


--generic=socket,in,25,localhost,5550,udp,headtracker --generic=socket,out,10,localhost,5551,udp,headtracker --config="E:/projects/fgmeta/data/Nasal/headtracker.xml" --prop:browser=/sim/headtracker


This additional setting text is used to start FaceTrackerNoIR - it works as a command line parameter, but will not work in the launcher additional settings textbox text.

FG as a short cut with the following works:

"F:\Program Files\FlightGear 2017.3.0\bin\fgfs.exe" --generic=socket,in,25,localhost,5550,udp,headtracker --generic=socket,out,10,localhost,5551,udp,headtracker --config="E:/projects/fgmeta/data/Nasal/headtracker.xml" --prop:browser=/sim/headtracker

To be clear is it only the ‘config’ option which fails? I am guessing it’s the embedded quotation marks which break it? Or do the generic options also have problems?


I was trying to debug fglauncher, but seems QT has issues trying to debug in windows.


What problems? debugging Qt on Windows ‘just works’, I do it most days (that I’m working on Windows)

Kind regards,
James

[James Turner]

> On 24 Jul 2017, at 13:32, Ron H <***@hotmail.com> wrote:
>
> It seems that the -config is not executed - I do get a window displaying the sim/headtracker properties. I assume the socket part works as I see the headtracker properties change in the property browser window. I always put quotes around folder path names assuming that spaces in names causes issues. Not at my machine currently will test later - Added the full path as I do not have FG_ROOT set in my system. Looking at the command line page in the launcher shows all the command line parameters and --config has been striped of the quotes. I would have assumed that the same format would work in both command line execution and --launcher execution.

The quotes should not be necessary for your particular example, but they are necessary if the path contains spaces, which of course it might. What I imagine is happening is that my arg-prase code in the launcher does not understand the quotes correctly, I will fix this.

> As to QT. I assumed debugging with QT should work and there is something wrong with my setup. I always seem to get a break just as the sections in settings are being processed. - again not at my machine currently. The debugger asks for qqmlcomponents.cpp - I don't have that file in my set-up. Overall, I am set-up similar to Jenkins. I have downloaded qt 5.6.1 single archive for x64.
>
> I have built/compiled OSG 3.5 debug, simgear debug and flighgear debug. QT is in a separate folder on the same drive. Debugging from VS2015. Any suggestions as to a better/different folder structure or debug environment would be appreciated. Debugging FG w/o --Launcher seems to work.
>
> I have not created a QT id, just downloaded the installer for QT 5.6.1. Are there additional files needed to debug QT?

Your setup sounds fine, and very similar to mine, so I don’t know why it’s not working - very strange. The official Qt download contains everything needed to debug code /using/ Qt - it doesn’t contain debug symbols for Qt itself, since those are huge, but also shouldn’t be needed unless you want to debug inside Qt itself, which I guess you don’t.

Kind regards,
James

[Ron H]

James,


Perhaps, its OSG 3.5, will try going back to OSG 3.4. Also are you using the QT creator IDE? There is also a QT toolkit? I did not install these elements. The error I get is only Abort() detected (or some such), nothing specific and nothing in the fg log. Thanks, I will continue see if I can get this debugging to work.


Ron


Windows 10, VS2015


________________________________
Sent: July 24, 2017 8:42 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Launcher - does not process additional settings textbox data

On 24 Jul 2017, at 13:32, Ron H wrote:

It seems that the -config is not executed - I do get a window displaying the sim/headtracker properties. I assume the socket part works as I see the headtracker properties change in the property browser window. I always put quotes around folder path names assuming that spaces in names causes issues. Not at my machine currently will test later - Added the full path as I do not have FG_ROOT set in my system. Looking at the command line page in the launcher shows all the command line parameters and --config has been striped of the quotes. I would have assumed that the same format would work in both command line execution and --launcher execution.

The quotes should not be necessary for your particular example, but they are necessary if the path contains spaces, which of course it might. What I imagine is happening is that my arg-prase code in the launcher does not understand the quotes correctly, I will fix this.

As to QT. I assumed debugging with QT should work and there is something wrong with my setup. I always seem to get a break just as the sections in settings are being processed. - again not at my machine currently. The debugger asks for qqmlcomponents.cpp - I don't have that file in my set-up. Overall, I am set-up similar to Jenkins. I have downloaded qt 5.6.1 single archive for x64.

I have built/compiled OSG 3.5 debug, simgear debug and flighgear debug. QT is in a separate folder on the same drive. Debugging from VS2015. Any suggestions as to a better/different folder structure or debug environment would be appreciated. Debugging FG w/o --Launcher seems to work.

I have not created a QT id, just downloaded the installer for QT 5.6.1. Are there additional files needed to debug QT?

Your setup sounds fine, and very similar to mine, so I don’t know why it’s not working - very strange. The official Qt download contains everything needed to debug code /using/ Qt - it doesn’t contain debug symbols for Qt itself, since those are huge, but also shouldn’t be needed unless you want to debug inside Qt itself, which I guess you don’t.

Kind regards,
James

[James Turner]

> On 24 Jul 2017, at 13:57, Ron H <***@hotmail.com> wrote:
>
> Perhaps, its OSG 3.5, will try going back to OSG 3.4. Also are you using the QT creator IDE? There is also a QT toolkit? I did not install these elements. The error I get is only Abort() detected (or some such), nothing specific and nothing in the fg log. Thanks, I will continue see if I can get this debugging to work.

Use Visual Studio mostly on Windows, VS2015 to be exact.

Kind regards,
James

[James Turner]

> On 24 Jul 2017, at 13:42, James Turner <***@kdab.com> wrote:
>
> The quotes should not be necessary for your particular example, but they are necessary if the path contains spaces, which of course it might. What I imagine is happening is that my arg-prase code in the launcher does not understand the quotes correctly, I will fix this.

Yeah, I had a dumb bug in this code, will push the fix tomorrow.

Kind regards,
James