David Toth

Here is what I came up with that works void in_t::handle_pagecycle(int button) { set<mfdpage_t*>::iterator it = a_pages.find(a_currentpage); debug_out(verbose,"in: handling page change from button %i",button); if (it == a_pages.end()) { debug_out(debug,"in: cannot find current page"); return; // not found } // *** NEW *** the button group of the last displayed page is not the button group we're displaying now bool btnGroupChanged = ((*it)->a_button != button); debug_out(debug,"in: setting current...

Another update… I check the size of the a_pages_button after it built and it says there are three elements in the set, however, the ++b_it; is still crashing. If I replace the ++b_it; with an explicit load of the first element of the set, "b_it = a_pages_button.begin();” then I can press the buttons and the first page associated with each button set displays on the throttle screen… On Jan 24, 2019, at 10:51 PM, David Toth dtoth12@users.sourceforge.net<mailto:dtoth12@users.sourceforge.net> wrote:...

[2019-01-24 22:10:35] [verbose] in: handling page change from button 1 [2019-01-24 22:10:35] [debug] in: setting current page {welcome} as inactive [2019-01-24 22:10:35] [debug] in: current page {welcome} now inactive [2019-01-24 22:10:35] [debug] in: iterating pages for current button [2019-01-24 22:10:35] [debug] in: iteratimg page [2019-01-24 22:10:35] [debug] in: inserting page [2019-01-24 22:10:35] [debug] in: inserted page [2019-01-24 22:10:35] [debug] in: iteratimg page [2019-01-24 22:10:35]...

OK… so I’ve gone through the code and increased the buffer sizes. The plugin no longer crashes on load and it doesn’t crash when the FP is edited. However, when the button is pressed corresponding to cycle FMS page 1 or something like that, I still get a crash… the last entry in the log is something about clearing the welcome screen. I’ve just recompiled the plugin with the debug flag set so hopefully I’ll get a dump with an actual line number and module instead of the general crash error On Jan...

What can I do to help? On Jan 20, 2019, at 12:05 PM, user2684 user2684@users.sourceforge.net<mailto:user2684@users.sourceforge.net> wrote: Hey there, I've spent a good amount of hours trying to find out the changes applied in the code referenced by ticket #44 (backup, external drives, NAS, etc.) without success. I'm afraid the code was in an old laptop I don't have anymore and for some unknown reasons I did not push it to the repo here (I guess because was still work in progress and then the activity...

I believe there was a cycledump.txt in the main XP11 folder...I don't recall whether it was empty, or didn't have any useful information... What was really strange was that while it was spewing "USS Nimitz" as the name of every navaid, it wasn't actually crashing until I tried to use the bound change-page button. Updating the SDK to the current release, and switching the define to enable v3 SDK support, fixed the navaid lookup but brought back the crash on load or addition of navaid to the flight...

Argh... so the progress was only temporary. I upgraded the SDK to the current version, hoping it would fix the problem with the name lookups and the crash in the handling page change, and the original problem is back... debug_out(debug,"fms_fp: Loading departure at index 0"); load_entry(0,departure); debug_out(debug,"fms_fp: back from load_entry - departure"); Plugin crashes after the last line of load_entry (which is a debug print that successfully outputs) This is what's expected [verbose] fms_fp:...

Excellent... it gets past the original crash point now, as you can see from the last log, but I just noticed that all the FP names are coming out as "USS Nimitz" which is a new problem that wasn't in the old logs (which had the correct names)