Re: [wpmac] Spotlight & Quick Look plug-ins now enable WPG previews
- Very OT, but Yasu and Onyx are two of many free tools that rebuild the Launch Services database. I use them all the time, because each time I revise one of my apps, the "Open With" menu adds a pair of parentheses (like this - () ) to the application's name, apparently in some attempt to indicate separate version numbers. It gets fixed by rebuilding the Launch Services database.
--- In firstname.lastname@example.org, "sardisson" <smokey.ardisson@...> wrote:
> Even purging my Spotlight db and rebuilding (after hacking away Pixelmator's qlgenerator's wpg support) didn't fix things for me. However, once I moved the Pixelmator app somewhere else and back (in order to make LaunchServices re-parse the .plist for the app and all of its plug-ins), new wpg files picked up the correct UTI and old ones started previewing (even with the bogus UTI). If I had remembered the LaunchServices bit, I probably could have saved myself the Spotlight db rebuild part of the "fix"
- --- In email@example.com, "em315" <em315@...> wrote:
> Very OTGoing further off-topic (for hopefully just one message more) ;-)
> but Yasu and Onyx are two of many free tools that rebuild the Launch Services database.I try to avoid a complete reset of the LaunchServices database, because it throws out any custom application<->file bindings you've established (except per-file ones, which are stored in the file's resource fork).
Usually moving an application or plug-in bundle to a new location and back is sufficient to update that application, though not always.
Sometimes the complete reset is the only way to fix things. :-(
> I use them all the time, because each time I revise one of my apps, the "Open With" menu adds a pair of parentheses (like this - () ) to the application's name, apparently in some attempt to indicate separate version numbers. It gets fixed by rebuilding the Launch Services database.:-O That's unpleasant.
Assuming you don't have multiple copies of the app running around on your disk, have you tried resetting the database's entry for just the app in question, rather than blowing away the whole database?
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -v -f /posix/path/to/app
10.5 (and up?):
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -v -f /posix/path/to/app
(I actually wrote an AppleScript wrapper around this that allowed me to drop an app on it, or choose the app via a filepicker, and trigger the update, no remembering and typing of long commands required.)