On Thu, Oct 30, 2008 at 4:50 PM, Blair McBride <[EMAIL PROTECTED]> wrote:
> Unfortunately, there's no easy way to debug errors like that in 0.1.2 > (its being fixed at the moment). So the best way is just trial and > error, removing commands until the errors disapears (or starting from > scratch and adding them until the error occurs again). Thanks - that was what I needed. I tracked it down to this: if (CmdUtils.getWindow) w = CmdUtils.getWindow(); else w = CmdUtils.getWindowInsecure(); When I just leave it as: w = CmdUtils.getWindowInsecure(); My errors go away, and my commands work again... Thanks! Derek. -- Derek Featherstone [EMAIL PROTECTED] tel: +1 613-599-9784 1-866-932-4878 (toll-free in North America) Work: http://www.furtherahead.com Blog: http://www.boxofchocolates.ca Learn: http://north.webdirections.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" 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/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
