New ISBoxer - Major Issue

[Mercurio]

Lax (or whoever can help),

I downloaded the latest ISBoxer today and it makes the game basically unplayable for me. I think the problem lies with something that was done with how characters are loaded. Some background on how I use ISBoxer:

I run what might be called a character agnostic setup. I have ten accounts. I have no set teams. I routinely switch different characters on various accounts one at a time on the fly. Once I log into ISBoxer, I can be logged in for weeks at a time without ever reloading it. I use ISBoxer to load up ten windows, then play whichever characters (and sometimes even whichever accounts) I want to in those windows. I only have ten names listed under the "Characters" section of ISBoxer and these names don't even match character names I play.

Need a shammy healer instead of a priest? No problem, I just type "/logout" on that window, double-click another character, invite her to the party or raid, and start playing. None of my macros are tied to certain characters and everything is mix and match.

However, with the new ISBoxer, this functionality seems to have been removed. When I loaded my characters in today, there was an odd message on all of my windows that said, "Character in wrong window? ISBoxer expeted So-and-so but got So-and-see. Some functionality may not work correctly." Basic commands still worked, but something major doesn't - if I ever swap windows, the swapped windows minimize - permanantly. I can't get them to show up again at all unless I use windows to completely close the window and reload everything from scratch. Its like playing WoW with no monitor. And unfortunately I found that I'm just not skilled enough to play with no visual or audible feedback whatsoever. Edit: Actually, it looks like all the windows are still running, but in the same screen area, so I can only see one at a time.

So, my immediate question is, is there any way to turn off this forcing of the window name to be the same as the character I load that was introduced in the latest build? Or is there another work around?