B-52F: Autopilot cleanup, previews, states, latest yasim version.
B-52F: Autopilot cleanup, previews, states, latest yasim version.
B-52F: add DME to mini-panel, revert vacuum system changes (not needed)
B-52F: add DME to mini-panel, revert vacuum system changes (not needed)
B-52F: Maintenance update. Instrument cosmetics and operation. Rudder steering added.
B-52F: Maintenance update. Instrument cosmetics and operation. Rudder steering added.
One more fix to "mag headings": The lib gives EAST variation as POSITIVE, so we must SUBTRACT it
Two fixes to showing ILS freqs in airport diagrams.
Cool. I got your message on how you are building. I'll try to get my local environment setup for building/testing on Windows. Happy to help in any way I can. Your prompt reply was much appreciated.
Cool. I got your message on how you are building. I'll try to get my local environment setup for building/testing on Windows. Happy to help in any way I can. Your promp reply was much appreciated.
Hi Trevor. I love this program, just started using it with flight gear, but I noticed that the mag var applied to my KLAX->KSFO was very wrong, like 47 degrees. I found the problem: the newer Geomagnetism.java expects its params to be in (long, lat) order, but Plan.java and PlanEditor.java were sending them in (lat, long) order. I make a fork and fixed it... tests correctly now (KLAX mag var about 12). I submitted a merge request if you agree this is the correct fix. Also: I got eclipse to MOSTLY...
Fix magnetic variation bug: long/lat params were reversed
OK, on the assumption that there is no good reason for these 2D panel action bindings to be in the property tree, I tried a different fix, to panel_io.cxx. It just gives the loaded xml binding node to the SGBinding instead of copying it to the global property tree first. This also works and seems not to cause any unintended problems I could find in testing. The attached patch (for 2020_3 only, but NEXT is similar) shows what I tried.
OK, I set breakpoints as advised, and neither one fired: FGPanel::doLocalMouseAction() and FGPanelPickCallback::buttonPressed() I DID notice that FGRenderer::pick() was being called (in Viewer/renderer.cxx), and it passed the click on to FGGroundPickCallback::buttonPressed() (in Scenery/scenery.cxx) if there was terrain behind the point on the panel that I clicked. And then I got lost. :)
Yes. I'll be back to the computer later today and will try as you say.
Thanks. I agree that my patch is, well, just a hack. I wanted to confirm that I knew what was happening, and did not want to break any code outside of the panel bindings. My thought was that SGBinding destructor could/should handle it, but it does not seem to.
Clickable HotSpots (actions) on 2D cockpit panels not working on NEXT
I guess the attachemets did not happen... trying again with them.
Switching between two 2D cockpit panels bogs down quickly