onox

I think because the "external temperatures, engine temperature taken into consideration" part is not implemented, we should move this issue to 3.8 feature freeze.

I'm going to revert this change, because the windows aren't guaranteed visible on small screens.

You could attach a listener to `/sim/startup/xsize` and `/sim/startup/ysize`. But I don't know how to get the dialog object. I couldn't find any Nasal code that does something with aircraft-dialog.

@wlbragg Yeah, just setting the x to 0 (or a small value like 10) might be an option.

That's not really automated. I prefer something like creating a [webhook](https://developer.github.com/webhooks/) which can send a HTTP POST to some URL.

> For having a fully automated setup that you push to yourselves (i.e. a git mirror on SourceForge), you'll probably need to coordinate with Torsten on the mailing list on...

If you want, I can write a shell/python script that does all this (JSON fetch, sha compare, shallow clone, rsync, commit) and then post it here.

> Arguing to have the c172p aircraft removed from the FlightGear core completely will not go very far on the mailing list. Where am I arguing that the c172p should...

I'm not sure whether I should commit the fix for this issue. I can work around it by using `/instrumentation/heading-indicator/indicated-heading-deg` in the instruments and then adding a `` that connects...

It's not just the kma20 instrument that has this problem. Other parts of the cockpit have this as well. The reason is because the sounds are activated via a Nasal...