On 27 July 2015 at 18:31, Thierry Goubier <thierry.goubier@gmail.com> wrote:
Le 27/07/2015 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..
Esay Igor, just use a code event tracer as for example Jejak, and all you describe below won't happen. Or an event logger, or metalinks, or anything.
I don't understand. You have the tools, why don't you use them?
Perhaps because i unaware of them? And while i agree that using robust tools would help, i don't see how tools can help with "unkilling" an image which you just killed by own hand because of mistake you made :) About Jejak, i only found this: http://lists.gforge.inria.fr/pipermail/pharo-project/2012-July/067679.html Where i can read bout it? It sounds very useful indeed. Thierry
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.