@tshirtman I'm not sure. I'm using the 3rd party TopDown engine, so there is a LOT of code I didn't write myself.
@peterdrake usually, being able to observe the bug in a much simplified environment allows understanding its condition better, and if the bug is still there and you dont understand it, at least you can share that example to the devs of the code you use, and ask if this is indeed a bug, or something you did incorrectly. The less code they have to look at, the easier the can answer that question.
@tshirtman Yeah, that's probably the way to go next. Of course, I was lazily hoping someone would say, "Oh, I've run into that many times. Here's the fix..."
I have to deal with some other pressing issues first, but then I'll try to rig up a minimal example.
@peterdrake arf, that can be troublesome indeed.
When i don't really have an idea where the bug comes from, i just simplify, until it disappears, or can be observed more easily because there is much less logic going around.
There are two ways to go about it, one is disabling/removing any unrelated part of the code you can, while still having it running, the other way is the opposite, to start a new version, as simple as possible, adding only the parts you need to recreate that situation.