I was just wondering how you guys debug your morphic programming. There is probably something wrong in the way I do. I cannot imagine people have been doing some morphic for so long without having a simple way to debug it. Cheers, Alexandre On 14 Feb 2009, at 18:26, Gary Chambers wrote:
I'm sure I can come up with something... you obvioulsy want some kind of debugger if an error occurs. The taskbar works effectively synchronously with the display and should handle self inflicted errors. Other display errors *should* get managed by the #errorOnDraw thing, but not always it would seem.
Regards, Gary
----- Original Message ----- From: "Alexandre Bergel" <Alexandre.Bergel@inria.fr> To: "Pharo Development" <Pharo-project@lists.gforge.inria.fr> Sent: Saturday, February 14, 2009 4:53 PM Subject: [Pharo-project] Debugging with morphic
Hi All (and especially the Pinesoft crew),
When an error is triggered by a displayOn: method, the bottom bar is being filled with debugger windows. It then become hardly debuggable. Ideally, the system should not display a window if an error is triggered in the displayOn.
Do you have any recommandation/conviention/enhancement to prevent the image to hang when an error is signaled in a displayOn. This is really annoying.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.