Beware when you have some code that draws in a graphical context of some kind that can be called from two different places at the same time or called twice so that the first call not is finished when the second is called.
I have been hunting for a bug that crashed my game and simply closed the App with no warning due to a construction like this. Use Locks objects combined with synchronize in your renderers, handlers or whatever to indicate if they are active and not must be called to create some kind of race condition. Anyway bug solved and the App has been enforced and is now more robust…
I got the solution and improved it at stack overflow.
And during this fixing process I revisited and fixed another annoying bug that have been irritating me, even though it is a small thing, that players not will see unless they where told. So all in all I’m almost ready…
