Belkiolle posted:
That's exactly what they're doing and I'm not sure how to fix nor do I have any clue why they would make that change.
ein_stein2000 posted:
I've tried to find an easy way to fix but have given it up ... it seems like mythic is returning -1 instead of 0 for "null"/no data/nothing selecte/or you wanna call it since the last patch and I have no idea how to catch that
eggi541 posted:
I am still trying to find a work around on the -1s
I am still trying to find a work around on the -1s
I've tried to find an easy way to fix but have given it up ... it seems like mythic is returning -1 instead of 0 for "null"/no data/nothing selecte/or you wanna call it since the last patch and I have no idea how to catch that
That's exactly what they're doing and I'm not sure how to fix nor do I have any clue why they would make that change.
there is no way to fix it without mythic helping us

I think they did a code review along the implementation of the new training window and there they changed it without knowing what side effects they will cause ...
I think they used to return 0 instead of null when there was nothing to display (no object/no selection) and during the review they changed it to -1, what's a common way to return when "nothing is there". I can think of 2 ways to fix it: either they return again 0 or they give us a way to handle it, for example they add a <DontDrawWhenMinusOne>-tag
-----signature-----



>13</Y>