I suggest boiling the problem down to a 20-line-or-less example that uses real code, and that we can run to see the behavior you're experiencing. It's possible that in doing so you will have removed enough distractions that the problem and its solution become plainly obvious, in which case you won't need further help.

Even if that doesn't lead you directly to an obvious solution, it will provide us with something concrete to assist in debugging. Your current problem description lacks anything we can actually look at to say, "Oh, it's because of xyz. Try abc." And by boiling it down to a small test example it relieves us from the tedium of skimming through a couple hundred lines of irrelevant code to find the relevant parts ourselves (that's your job ;).