EXIT module not working

[sethtroisi]

Hey Stoermelder, I am super excited about using your EXIT module to chain a series of racks for an AV project.
I think the EXIT module is broken at head because of Rack 2 api changes? How can I help?

I used the latest module from the nightly tag but it didn't work. So I downloaded and compiled the module.

It looks like because the MB extension is disabled in b18ca9d#diff-5f6c4197f0142fbc04b0c77f4fe8294057a581a9f970721896e2c95abeec1e0c

When I uncomment the MenuBarEx::init(); I get a runtime error Rack: src/context.cpp:47: rack::Context* rack::contextGet(): Assertion threadContext' failed.`

I assume this is all known. What can I do to help fix the module?

[sethtroisi]

I made some headway by simply removing uses of APP from init(). This causes step() to not be called but I can call step() directly during trigger(). This "works" in that I see [5.485 info src/patch.cpp:251 load] Loading patch /home/five/.Rack2/patches/test2.vcv in the log but then the VCV Rack locks up similar to what you described in https://community.vcvrack.com/t/loading-a-patch-from-plugin/6430/2

[sethtroisi]

I managed to hack this back to working. my understanding is something like this.
When menuBarExButton::init() is called in a place without context (accessed when you call APP) it doesn't get added to the list of widgets and won't have step() called. If I call menuBarExButton::init() once from ExitWidget::ExitWidget(ExitModule* module) then context exists and everything works happily.