The calculator plugin is working fine for me. Submitting tickets is the best thing to do, as it means all the bugs are in the same place.
I've also uploaded a Universal build of the release to the downloads page. On Sep 23, 12:21 am, Daniel <[EMAIL PROTECTED]> wrote: > I'm not having a quit-immediately-after-opening problem, but rather a > quit-on-type problem. Basically, QS opens fine and I can access the > prefs, but when I invoke the QS window and start typing a search, it > never registers and QS quickly crashes. I haven't gone through the > full-reinstall process, so it could be a plugin issue, but I'm > wondering if anyone else has this issue? If not, oh well—I'll just > keep using B54, which works fine for me, but I'd like to keep up with > QS development if I can. > > On Sep 22, 3:34 pm, Matthew McCullough <[EMAIL PROTECTED]> > wrote: > > > I am experiencing the same quit-almost-immediately-after-opening as > > soon as I load the Services plugin as well. > > > Where's a good place to upload the crash reports? Don't really want > > to file a defect/ticket unless someone can certify that they want me > > to do so... > > > Etienne? > > > Thanks for all the efforts, > > Matthew > > > On Sep 22, 9:14 am, ellDov <[EMAIL PROTECTED]> wrote: > > > > Seems very buggy. Some of the plugins (the Services Menu Module for > > > one) seem to cause quicksilver to quit within 5 seconds of launching. > > > some of my triggers from a3 don't work or don't work right (the > > > command window in text mode, the command window with selection) > > > > I'm reverting to a3
