I have seen this behaviour in a number of different applications and I am absolutely certain that it is caused by the Wacom Drivers.
The proximity sensitivity has become too sensitive and I find that my stylus needs to be about an inch above the tablet for it to become disengaged. Changing the pressure to "Firm" seems to help somewhat. (I have trashed and re-installed the Wacom driver but it hasn't helped.)
My tablet is very old (an Intuos GT) and there doesn't seem to be a recently updated Driver for it. The problem is irritating but as I am not in the mood to buy a new Wacom tablet right now, I have just been putting up with the annoyance!
Running CS 5.5 on OSX 10.6.7 on a MacPro (2 x 2.4 Quad-core Intel Xenon).
Found this on the Wacom site:
This isn't the exact problem I was having but seemed connected. I have a spare Wacom pen and this morning I tried one of my reproducible bugs: resizing a window with a large InDesign file. Seemed to work just fine with the new pen. We shall see.
I will try removal of the nib tonight!
I have just changed the nib and the problem is fixed.
The old nib had lost about 1/32" of its original length and may have been pushed back onto the click contact in the pen as well.
Why on earth didn't it occur to me that there might be a connection between the fact that the tablet is old and the nib might be worn-out?!
Cheers, man... Points well-taken, and thanks for the note. I know Chris has probably been at this a long long time, so I can easily understand a natural aversion to situations that could lead to "false positives." I will see if I can get a couple example files uploaded tonight and send you some links. Coincidentally, I'm leaving town tomorrow and will have access to a relatively new iMac for a few days... so I'm planning on testing some things out while I have the opportunity. My hypothesis is that I will have the same issues that I do now with these types of files (i.e. those with moderate pixel dimensions, but dozens of layers and layer groups). I think the iMac may only have 4 GB of memory, (vs 24 on my current machine), so I may notice decreased responsiveness either way. I'll report back on what I find.
(Keep in mind, I have almost no programming knowledge, so please feel free to discard this if it's worthless speculation. Also—for me, this issue is almost always related turning the "eye" icon on or off, to make layers/groups visible or invisible... so that's my frame of reference.)
... my observations make me think that the mouse-up event or process (not even sure what terms to use) is designed to occur only after some other event(s) conclude(s). ...and that whatever normally triggers the mouse-up event is somehow bypassing it instead. I base this all on observing how this bug plays out in various situations.
If my line of thought above has any merit, the focus would naturally move towards identifying what types of things are leading to situations where the the authority over the mouse-up is either delaying or withholding the go-ahead. The obvious choices (again—in my own little pseudo-hypothesis here) would seem to involve screen redrawing, and maybe some other type of change to the GUI (e.g. the "eye" icon dis/appearing, the movement of items within the layers panel, etc.) The screen-redrawing thing seems potentially relevant since it can involve a lot of resources (presumably) which could involve withholding resources from other parts of the program (presumably, in my non-programmer mind, anyway).
I think I first noticed this bug when I clicked-and-held on a layer's "eye" icon and dragged downwards over several other layers' eye icons in order to (ostensibly) hide those in the same step. Instead of all of them turning off, the first couple turned off, and the rest stayed on—even though the mouse passed over them directly before I released the mouse button. Somewhere between my click and my eventual release, that event/process (or series of event/processes) was perhaps interrupted or stopped or whatever... it didn't seem to continue or complete. This example is one that recurrs a lot for me in regular use. Recently, I've noticed the following: that even though I clicked, dragged over a series of icons and then released, the mouse is still in the "down" state... and because of that, without pressing the mouse down again, I can simply pass the cursor over the icons that didn't turn off the first time. So essentially, this is the strongest link of a behavior to my theory above. The first time the mouse passes over those layer visibiltiy icons, some of them don't receive the instructions to "turn invisible"... yet, after a delay, you can pass the mouse (now in a physical "up" state) back over them and they'll turn off/invisible.
Anwyay... hopefully there's some little detail there that sets of a lightbulb for someone... Thanks for the interest!
P.S. Re: the WACOM issues—the first things I generally looked to when this started happening were my WACOM tablet and my 3Dconnexion SpaceNavigator. The issue I'm having isn't related to those issues, but it's good to point them out anyway... they're definitely worth eliminating when trouble-shooting (which I did).
P.S. This issue only happens for me in Photoshop (CS5.x-only). I use Illustrator (CS5) very heavily as well, and have never had problems. I don't use InDesign, or any other Adobe apps much.
Damaged fonts can cause various problems in Photoshop, some of which don't appear to be font-related. The following solutions are listed in order of easiest, and most likely to locate the damaged font, to more challenging or time consuming.
For me deslecting Font Preview Size solution worked. To do this goto (Mac) Photoshop/Preference/Type and deselect the Font Preview Size.
Click on the below link to see more solutions.
Hope this is any help.
After working on smaller files for a couple weeks without any problems, I opened up one of my very large files (4.38GB when opened in PS and with 197 layers in 37 layer groups) and, voilá, the problem was there, big time!
That explains why this problem is not that common - most people do not work on these kinds of large, extra-many-layered files. My assumption is also that Adobe probably does not do extensive testing on these kinds of files but rather on more moderately sized files.
I am now 100% convinced that this is a PS bug. 100%!
I also know quite a few people who work on these kinds of files as professional retouchers and most of them are way too busy to participate in any online forums, but will rather live with it and hope for an update sooner rather than later. I actually know this from discussing various previous issues with them. They just don't have time to deal with finding the right forum, posting, replying, etc...
Another explanantion why there aren't that many complaints coming forward.
I have the same problem with the layer in the layer palette getting stuck when clicked. I also noticed a host of other problems, including, depending on what file I'm working on, getting the 'File was saved outside of Photoshop.....' alert constantly while trying to save.
I noticed all my problems beginning after installing Suitcase Fusion 3. Any correlation with anyone else?
I have the sticky mouse problem as well. I see it on more than just sliders however. I do have a wacom tablet. I see it happen with the mouse and the wacom pen. I see it with sliders as well as brushes. If I had my guess, I would agree with a problem in photshop with event handling of mouse press/release.
This bug is very disruptive, particularly when it happens with a brush.
I work with large files, with many layers almost all with masks. If I was debuggung I would start there. It could only occcur when resources are close to used up or process time is in high demand. I do notice that when it happens with the brush, the system seems like it boggs down, and occasionally will pinwheel. could be related, maybe not.
I will try to pay more attention to exactly what I am doing when it happens, and post it here.
@chris cox: what are you guys doing to try and replicate the issue? or what have you tried?
Europe, Middle East and Africa