You can disable HyperDock from the HyperDock Preference Pane, and Photoshop's hotkey's work again, and re-enable HyperDock and cause the issue. I'll chime back in if I have the problem arise again.ĮDIT: HyperDock 1.0 also causes the issue. It's like I had to reboot once with it disabled, and now everything's fine even if I'm running Dropbox. I've, interestingly, also restarted Dropbox and rebooted, now allowing it to start at boot again, and I'm not having the issue, even with Dropbox running. I also had LogMeIn running, and I disabled it at the same time, but I don't know that this had anything to do with the error. and disabling Dropbox solved my problem. Hey guys, I wanted to let you know that I had a similar problem, as seen in this thread: But even if I force-quit these processes I can still trigger the bug. So I tried to find a process that would be shared between those apps and could be the culprit, like CS5ServiceManager or AdobeCrashDaemon. It seems the bug is triggered for all CS apps at once, even the ones not launched! This dialog is supposed to show only if you press Option while Photoshop launches. Ie: I launch Illustrator, trigger the bug with Things, then if I launch Photoshop it immediately asks me if I want to erase the prefs. Once triggered in one CS app, the bug is immediately triggered in other apps from the CS suite too. In Things I tried Shift-Ctrl-Option-Command Space, Ctrl-Option-Command Space, Shift-Ctrl-B and a few others, and it didn't make any difference. So it seems they're only "stuck" in CS, not at the OS level or in all the other apps I've been testing. If you open OS X's keyboard app, Control Command Shift and Option don't show as down. Every non-CS app I've tested worked normally while the bug was triggered in CS. Lightroom doesn't seem to suffer the bug, but it is not part of CS. Once triggered, CS apps (Illustrator, Photoshop, InDesign…) act as if Control, Command and Option are always down. No idea if it has anything to do with the problem though, just writing it down in case it helps. The main difference between the quick entries is that the "quick entry with autofill" uses OS X Services to get any selected text in the frontmost app and some other informations, as described in Cultured Code's wiki: Still it's good to have this fix when we're in the middle of some work, instead of having to log out.
Using the "fix-upper" worked, until I used quick entry with autofill in Things again.
Oh and I noticed this issue way before 10.6.5 too. It's not the only way to trigger it on my Mac: I never used this combo before I read this topic (I actually had to change it's keyboard shortcut to use it because of a keyboard shortcut collision with another app, so I'm 100% sure I didn't use it by mistake.) I normally only use the standard quick entry that doesn't trigger the bug. The normal quick entry never triggers the bug. I can also reliably reproduce the bug with Things, as described above: as soon as I use the "quick entry with autofill" combo.
0 kommentar(er)
