On Feb 1, 12:28 pm, "Ryan Gahl" <[EMAIL PROTECTED]> wrote: > Matt, in any event based language/system... it is considered best practice > that if any 2 event handlers rely on the order of their execution, then they > should be combined into a single handler (or one method calls the other). > ...
I understand your point, and I appreciate the comments. I guess handlers don't really have to execute in order, but I assumed it would make sense if they did (especially since that's the way FF does it :D) Anyway, of course, in most cases, I could wrap my functions into one, but my problem is that I don't have access to one of the Event.observer registrations since it's been wrapped up in output produced by PHP. My functions are dependent on that handler to be called first. And I don't want to change the PHP because the PHP classes are suppose to abstract the implementation of the tool, and having to register a function outside the PHP that was created inside the PHP breaks that abstraction. Right now, I'm just setting a timeout on a function (that calls my functions in order) if the element that I'm dependent on doesn't exist yet. It will continue to set an additional timeout every time it sees the element doesn't exist. It seems hackish though. But right now that's the only way that seems feasible / makes me happy :P Works like a charm though, so maybe I'll just stick with that. Again, if you have a suggestion, I'd appreciate it. Thanks, Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
