GeneralWriteDelay and GeneralCmdDelay not saved? (2.0.1049.0)

BigJacko

Hi Stephen,

My apologies for absence since March! Life is what happens while you're busy making plans, as they say, eh?

I am delighted to see so many useful new changes to the GIT project and looking forward to completing my configuration sets for my GF-MCP and my Aerosoft Extended A320 in particular. The organisational changes with XML files and the ability to load them 'unescaped' makes for huge clarity, I must say, and I thank you for that. I may yet get my JS4100 resolved (haven't tried yet, but it's on my list).

However, I did stumble upon something which is probably very, very minor, but seemed at odds with your likely intentions.

I've noticed that in the user.config file in C:\Users\User\AppData\Local\PollyPot_Software\GoFlight_Interface_Tool.e_Url_zuk3tbnct12hreu2xe45qri2hcd4ayjr\2.0.1049.0

the GF-MCP-specific write and command delays get stored thus:

            <setting name="MCPDelayedWrite" serializeAs="String">
                <value>50</value>
            </setting>
            <setting name="MCPDelayedCmd" serializeAs="String">
                <value>65</value>
            </setting>

and appear (correctly enumerated as 50 and 65 respectively) in the top right of the MCP tab page. However, the Settings tab page shows a similar pair of Write Delay and Cmd Delay sliders, but no matter how I position these, followed by a Save, or a Save/Quit, or just a Quit, they always default back to zero on the next GIT relaunch from cold. They appear to have a home in the same user.config file at:

            <setting name="GeneralWriteDelay" serializeAs="String">
                <value>0</value>
            </setting>
            <setting name="GeneralCmdDelay" serializeAs="String">
                <value>0</value>
            </setting>

but these never seem to change or get written.

This may be entirely intentional, or some legacy aspect that simply isn't necessary or implemented in my specific situation, but I thought I'd better mention it, just in case. Certainly the fact that the adjacent Button Hold Time and Bespoke Event Time do seem to save correctly, indicates that the sliders on this Settings tab are not entirely vestigial yet, so the non-working Write/Cmd Delay ones cause a raised eyebrow - even though I don't actually know their significance!

Hope this isn't a timewaster. Thanks again for the improvements.

Best regards

Neil

admin_pps

Hi Neil,

Good to hear from you again. The logic for those is fairly convoluted, depending upon which devices you own. I'll check the code and come back to you shortly.

Thanks for the feedback

Steve

admin_pps

Hi Neil,

Those sliders are for GF166's, GF46's and GF45's. If you don't own any of those, the sliders always default to zero regardless of what you set. I'll change it so that they at least return to default values and not zero.

Best wishes
Steve

BigJacko

Aha, thanks Stephen. Figured it would probably be something like that, but the indication that they where 'default' or generic (or whatever it was) made me wonder whether they should still be saving what I input. Perhaps a tooltip or note adjacent  - to the effect that they're unconnected if you haven't the right kit - might stop others asking the same question in the future?

 

Thanks for looking into it, anyhow. At least I know nothing ill will come of their apparent deafness in my case!

 

Cheers

Neil