Axel Dörfler wrote:
Adi Oanca <adioanca@xxxxxxxxx> wrote:
* removed adding "be:transit" stuff in the EventDispatcher - this is now only done
client side (or will be, with the next commit).
Maybe you/we are rushing into things...
I agree, ATM doing mouse transit on client side is OK, but please have in mind, in the near future we want to have non-rectangular windows and views(for example rounded buttons) and I guess you don't want keep another region or a transparency map on client side because the frame rectangle would serve you nothing.
Maybe we should move this functionality to ServerWindow, but maybe there would be too much work for it then.
Haven't thought a complete solution yet, but I just wanted to point out this future problem. I really think view transit should be done server side, more exactly - the place where the visible regions are kept.
There is a little oversight on your part: the client side implementation doesn't rely on coordinates at all - it will work with non-rectangular shapes just fine.
I'll never spoke again before I consult the code :-P.