P: CS4, CS5, CS6, CC: Cursor disappears on Mountain Lion (MacOS 10.8)

The hundreds of RADAR bugs that we have filed on OS code crashes, file system problems that lead to lost files, OS memory leaks, etc. Those tend to be prioritized above "cursor sometimes disappears".

I'm sorry you got a bad support person and incorrect information.

But please let Apple know that you would like this problem fixed.

I only ever had the problem of a disappearing cursor with Photoshop, after I installed ML. When I spoke to the Adobe representative, they told me that I had to buy CS6 because CS5 was not compatible with ML.

I immediately went and bought CS6, hoping it would do away with the problem. I can report that the cursor disappears far less than it did on CS5, but it still happens often enough.

(I also have a MacBook Pro, and luckily I didn't upgrade to Mountain Lion there, so there is no disappearing cursor in Photoshop on that computer.)

I don't really care whose fault this is. Like everyone else on this forum, I am not able to work properly, and after paying for professional programs that have worked in the past, I expect them to work in 2013, too.

safari, MS office, iChat, On the Job and CS6 are all the apps I launched in the morning, and quit at 5pm. SO they were ALL being used everyday. But only CS6's cursor disappear. So it is not the case of "the other apps not being use less CS6 here".

we can't tell apple to fix this bug without knowing the radar #. That is the best way to reference them. Since all the technical details are all listed in the radar.

Chris, since i am having this problem with 10.7 with only CS6, I should downgrade to 10.6 then?

What are all these other "serious bugs" that you speak of?

File bugs and tell them how it impacts you.
Write on their forums, and tell them how it impacts you.
Give them some reason to prioritize this over all the other serious bugs they need to fix in MacOS 10.8.

What is the most potent way of telling Apple how important this is?

No, it means that you have a very small sampling of the problem.
And since this is a known bug in MacOS that affects many application, it could hardly be an Adobe problem.