Hi igor

I imagine that quite well. Terribly tedious. I was wondering what would be a good architecture to handle it in the future: probably the approach of guillermo
wtih one image poking another one

Well, i had idea once, to implement a sandbox window..

which works completely separate from main UI and all in it is err.. sandboxed. :)

Everything comes in, nothing comes out..

In that way, if something horrible happens in sandbox , it doesn't affects the hosting environment.. Unfortunately it is easy to imagine as concept, but quite hard to implement given the state of our current system.

The main barrier for this is tons and tons of global state and singletons everywhere.

��

Stef


Le 27/7/15 15:42, Igor Stasenko a ��crit :

Nothing here is about things to fix,
but rather about how impossible to debug event handling in system that runs and relies on very same events..
I had very annoying problem with mouse move handling and processing it correctly, and i finally solved the problem after number of attempts to track down where problem lies in..

So, here is small list of problems i faced:

��- broken image (image won't start up) , because i send unimplemented message in critical place, thus image simply non-responsible/crashing immediately after startup. Easy to fix (sarcasm)

- debugger window spam on every event (because of DNU/other exception).
A slightly friendlier problem than above :)

- and last one, if you break some event handling/delivery, even if image "behaves" you simply left without events doing what is needed, means you got another form of a broken image, which you cannot use anymore and need to start over and revert the changes you made.

- veeeerrrrryyy slow event handling, because of printing every event into transcript , trying to see where the shit lies.

- decrypting kilometers long event traces to see what goes where

But when things finally start work properly, you feel excited :)

:)

--
Best regards,
Igor Stasenko.

--

Best regards,
Igor Stasenko.