Quote:
Originally Posted by cbkbud
But if it was expanded to dynamic events, then why should we be forced to start them with on?
|
I'm just pointing out how at the moment you would do something like:
this.catchevent("GraalControl", "onResize", "onGraalControlResize");
instead of:
this.catchevent("GraalControl", "Resize", "GraalControlResize");
Things like scheduleevent() and trigger() always prefix the event name with "on" to show that its an event so catchevent() should reflect that Graal event function names always start with "on"
I believe that should be fixed by Stefan and he should give people a warning ahead of time so they can fix their scripts.