>>I already surrendered with this one :)
>>Cetin
>
>Aww, c'mon, that's not like you. How about the ol' divide and conquer method:
>
>simplify your grid and its environment until the problem goes away, and then back up a bit, and see what causes the problem. I have seen this from time to time, but have always been able to fix it.

---

Hey you're "spilling salt on my wound" (tried to translate a Turkish saying:)
That's the main problem. Framework code is so spagetthi code that I prefer surrender than to divide it (Command and Conquer wellcomed:). Worse its only debugging support is to log memory vars and display status output and throw you out if you have a bug :) Yes to make that work I explicitly "hook" bugs too :) No way to invoke debugger (or I don't know) and break, trace, watch etc. (awfull, awfull, awwwwfuuuuulllllll:)
When I have really plenty of time I can deal with it.
Cetin