Thank YOU tiennou for your work :D Something that I thought Howard had brought up, but he hadn't the 'trigger' column of the triggers pref pane doesn't always show the whole trigger for me, (funnily enough I've just checked now and it's working). So if I have a trigger that's CMD + OPTN + CTRL + L only the "CMD +OPTN + CTRL" will show up. Annoying!
On Jun 25, 9:48 pm, Etienne Samson <[EMAIL PROTECTED]> wrote: > >>> The menubar icon (at the top right of the screen) doesn't appear. > >>> I checked that the preference was still set correctly and > >>> unchecked and checked it. > > >> This one is posing me problems, as I can see it working here, but > >> some people have reported that it fails. I'm suspecting something > >> in QS's Application Support folder, but I haven't been able to > >> reproduce... > > > Still happens, let me know if there's info I can send you to help > > you debug. > > I guess I'll need the complete QS App Support directory (or a way of > creating an App Support dir with ß54 that will fail under ß56). Maybe > try launching with the Option key down. > > BTW, quick debugging tip : > QS uses several environment variables to decide what's logged to the > Console or not. Holding Option at start enable some of them, but here > is the complete list : > verbose > NSDebugEnabled > QSDebugRanking > QSDebugMnemonics > QSDebugPlugIns > QSDebugMemory > QSDebugStartup > QSDebugCatalog > > and then you can run QS with the following script (put it somewhere in > your PATH) : > # !/bin/sh > QSAPPLICATION=/Applications/Quicksilver.app/Contents/MacOS/Quicksilver > verbose=1 NSDebugEnabled=1 QSDebugRanking=1 QSDebugMnemonics=1 > QSDebugPlugIns=1 QSDebugMemory=1 QSDebugStartup=1 QSDebugCatalog=1 > $QSAPPLICATION > > and you should get all QS logging in the Terminal window ;-). > > I'll try enabling all of them by default on the alpha builds, and > redisable them when I'll be nearing release. > > > > >>> At least one address book contact that had an image didn't display > >>> the image in Bezel. I think the old version of QS did this > >>> sometimes too. > > >> I checked and it didn't have any problem displaying images. Maybe > >> it's an exotic format ? More info would be fine ;-). > > > My formats are all jpegs. Seems to be working better w/ 3820. I'll > > keep looking and see if it recurs. FYI, with the last one I tried, > > I looked up my friend greg, saw no image in the bezel, did show > > contact and Address Book opened (it was already running) and I saw > > gregs contact including image. When brought him up again in QS the > > pic was in the bezel. > > It could be caused by Quicklook taking some time to create thumbnails > (since every image displayed is now going through QL), but I haven't > checked the AB module source code specifically. > > >>> The ⌘ column under triggers is fixed width and some some extra > >>> glyph that looks like the left half of a H following the hotkey > >>> icon. > > >> Fixed in the branch. > > > Still see it in 3820. Though I think that what you're saying, fixed > > in the next release. > > Exactly ;-). > > >>> My only mouse trigger (and my most used trigger) doesn't work. It > >>> does Hide Current Application and is set to activate on mouse > >>> entering the lower left corner. When I checked it wasn't > >>> configured that way and when I set it to be that QS crashed. > > >> I don't have the source to the Mouse Triggers module (which handles > >> this stuff), but I would be interested in the issue report anyway. > > > Still fails, which makes this version difficult for me to use. > > Then create an issue for this one too, attaching the crash report. > I'll take a look at it when I'll have the Mouse Triggers module source. > > Thanks for the input (all of you!), I'm quite impressed by the 288 > downloads b55a1 got in 4 days ;-). > > tiennou
