|
|
Double clicking QC Plugins in finder on Lion KinemeCore once was the default application for QC plugins and moved them to ~/Library/Graphics/ —> QC Patches || QC Plugins depending on the API used to make them. Has this functionality been removed by running KinemeCore in Lion? I seem to remember this has come up already but can't find a thread discussing it.
|
That should still work. Maybe since there's not an installer anymore, it stopped whatever sets KinemeCore Plugin Installation Assistant from associating a plugin file with it? That doesn't seem quite right though.
Try selecting a plugin and hitting Option+Right Click, and see if you get a menu that lets you open it with KinemeCore Plugin Installation Assistant. If not, find the KinemeCore plugin on your system, and go into the bundle's resources. Double click on the installation assistant, get the prompt that you're opening it for the first time, etc. After that your system should associate it with the plugin file extension.
Plugins (and unoffical SDK ones) were associating with Terminal.app. I double clicked the KinemeCore Plugin Installation Assistant and got an error. I get the same error message when I double click a .plugin now — so the good news is they're associated now I guess.
Process: launchd [2856] Path: /Users/USER/Library/Graphics/Quartz Composer Patches/KinemeCore.plugin/Contents/Resources/KinemeCore Plugin Installation Assistant.app/Contents/MacOS/KinemeCore Plugin Installation Assistant Identifier: net.kineme.KinemeCore_Plugin_Installation_Assistant Version: ??? (???) Code Type: X86-64 (Native) Parent Process: launchd [138] Date/Time: 2012-05-16 15:00:11.747 +1000 OS Version: Mac OS X 10.7.4 (11E53) Report Version: 9 Interval Since Last Report: -155055 sec Crashes Since Last Report: 8 Per-App Crashes Since Last Report: 3 Anonymous UUID: 8E2C7249-CAB0-4515-AED0-15AE78DAB4B0 Crashed Thread: Unknown Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028 Backtrace not available Unknown thread crashed with X86 Thread State (64-bit): rax: 0x000000000000000e rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000 r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000 r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028 Logical CPU: 0 Binary images description not available External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 1 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 11713 thread_create: 2 thread_set_state: 0 Model: MacBookPro8,3, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 8 GB, SMC 1.70f5Maybe you could try clearing your cache or kinemecore preference file, or redownloading kinemecore, though it seems to be a longshot. Maybe if you had an older version installed there could be some Preferences folder plist setting of the older version running afoul when the new one loads. Sort of unlikely, but you never know.
If you're running it from the User location, maybe you could try running it from the normal /Library, keeping other stuff in ~/Library.
Yes, that's a known issue --- KinemeCore's Plugin Installation Assistant doesn't work on 10.7 (see the release notes on http://kineme.net/release/KinemeCore/052).
My apologies.