When I use Exposé or Spaces, say to grab some filler text from the ol' Lorem Ipsum generator, and switch back into Photoshop, the image intermittently ceases to redraw correctly.
For example, if I select some text, delete it and type some new text in, the changes don't appear until after I've typed the text, applied the changes, then switched tools. Or say I paint something with the brush tool, and then undo the change. The History panel will change, but the image appears *exactly* the same, until I either switch tool, move a layer with the move tool, paint something else with a brush or anything else that seems to "force" a redraw.
The problem goes away (on my 9400M at least, I haven't tested this "solution" on the 9600) if I open the Logout window, or click on a window in the background to give it focus. This does not occur if I disable OpenGL acceleration, but software mode looks pretty ugly, and the smart guides (which I love), run absolutely horribly.
I have a Macbook Pro – one of the new unibody ones, with a 9400M and a 9600M GT. 2gb RAM, Core 2 Duo 2.4ghz, etc. I'm using Leopard 10.5.6 with everything up to date.
This problem is intermittent, seemingly happening less frequently when using a 9400M as opposed to the discrete 9600M GT. It happens on both the laptop's screen, and an external monitor.
Has anybody else hit the same issue, and found a more permanent workaround? Any beta drivers I should know about?
Thanks in advance.
Take up the Spaces problem with Apple because Adobe can't fix Apple's software!
No one here can speak for Adobe. We're not here to defend Adobe, nor to explain why Adobe does things one way or another, nor to apologize for Adobe.
We can describe things as they are to you, and sometimes we can suggest workarounds; but if you want to address Adobe, use the Contact button at the top of thos page.
If you have problems with Spaces, you need to take them up with Apple - because they are the only ones who can fix Spaces.
I'm sure you'll tell me "I've seen other applications with bugs in Spaces, even Apple products" and that may be but in my experience using Spaces with a ton of apps nothing even approaches the train wreck that happens with any CS4 app.
And I fail to see how Adobe can look like a fool when you are seeing bugs in Apple's product.
Adobe isn't doing anything wrong here, and has followed Apple's guidelines very closely. But Spaces has problems, and those can only be fixed in the code for Spaces, by Apple.
I think 3 words sum it up: Spaces is buggy.
Neil
And I fail to see how Adobe can look like a fool when you are seeing bugs
in Apple's product.
Then you need glasses because it affects YOUR product! Have YOU talked to Apple about those bugs?
If people are experiencing problems with an Apple feature that only seems to happen with Adobe apps, it's perfectly logical to assume the problem lies with Adobe. It doesn't matter if that assumption is incorrect - perception trumps right and wrong every time! (fortunes are made and lost on perception) And that's exactly why you keep seeing people complaining about this issue - repeatedly and argumentatively, even after you inform it's Apple's problem.
Spaces apparently works fine with PSCS3. You radically change the GUI in CS4 and Spaces is broke. What's the logical conclusion, regardless of whether or not that conclusion is accurate?
I don't use Spaces so it doesn't affect me one way or another, but frankly, this "not-my-job", "not-our-problem" attitude sucks. These are still YOUR customers. People don't care who's at fault - they just want the problem fixed.
Rather than just pointing a finger and "talk to Apple", it'd instill confidence in YOUR customers if the response was something a little more helpful and understanding.
Something like, "yeah, we know there's an issue - we've reported it to Apple and we're working with them any way we can so they can get it resolved.", would show you actually cared about the people who keep you employed.
Caring about a customer ... Gee, imagine that?
-phil
I'm sorry you read an attitude into my posts that does not exist. And I'm sorry you haven't noticed how many times I've already said that we have worked with Apple, we have filed bugs, but that we can't do anything about it ourselves.
Adobe has done what we can, and all I can do now is tell you is to contact the people who can do something about the Spaces bugs: Apple.
What more can I say? "Sure, I'll go wave a magic wand at Apple tonight and fix their code for them?"
Adobe's software is working within Apple's own specifications here. Adobe has been sending over its emissaries with its findings and offers of help for quite some time, but you want to shoot the messenger.
As I see it, the most valuable thing that you and others can do is to bang as strongly at Apple's ramparts as you are here and let them know how important it is to their customers to get the problem resolved.
Neil