> Well, I'm not really an expert on Hook, but not propagating die sounds
> like a bug. I'd be curious to know how you fixed it.
As you can imagine the fix wasn't difficult, or I wouldn't have been able to
do it:)
My use of the word "propagating" was probably misleading. When an event is
run, any error is trapped in an XS equivalent of an eval block - once
trapped the error is displayed to the user a message box, and the program
keeps running if you click ok. The hooked code it wasn't calling
ProcessEventError which displayed this message box, so any error would be
effectively ignored.
I changed the code to call ProcessEventError on an error, and while I was at
it I moved a string comparison check in ProcessEventError to only be
performed when there is an error - which should mean that all events will
run slightly faster (we're talking by a tiny amount).
Cheers,
jez.