Possible bug with custom window title and filters?

Ok, so I had my "next window" mapped key's filter set to this: "(is1,is2,is3,is4)&all" for my 4 man team with the 5th slot as a dxNothing window.

I created a new character set with a 6 man team (using all the same key maps) and adjusted the filter to "(is1,is2,is3,is4,is5,is6)&all". Everything worked fine with swapping on the new config. But later on when I fired the 4 man team back up, I noticed window swapping was glitchy. I quickly realized that it was trying to swap to the dxNothing window which was called "is5" in my 4 man team.

I then renamed that slot to "dx1" or "dxnothing" in ISBoxer and exported. But whenever I tried to swap it still kept focusing the dxnothing window. It's like even though the window "title" is different, somewhere internally that slot is named "is5" and the filter still includes it.

Anyway, I just split my next window mapped key into 2 separate keys with the appropriate filters in each and each assigned to only 1 character set and all is good.

I'm just giving a heads up about the filters since the custom window title is a new feature and didn't seem to work in this regard (at least for me).

[lax]

The custom window title is unrelated to the instance name, which indeed would be is5. Not a bug.

What you want to do to exclude dxNothing is add "&~dxNothing" (assuming that the Character in ISBoxer is actually named "dxNothing")
"(is1,is2,is3,is4,is5,is6)&all&~dxNothing"

Note that &all is probably not required in any case. The default is actually "isboxer&~dxnothing".
"(is1,is2,is3,is4,is5,is6)&~dxNothing"