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

They're not public. But sharing the number on Twitter gives a headsup to the people who work at Apple that folllow any devs on twitter. The actual radar number is not super useful for anyone outside Apple. But for anyone inside Apple, it's insanely useful.

There is OpenRadar, which people post stuff into if they want to make it public. And then link the radar number for other developer to dub. A community thing making it easier to see common complaints and sometimes get comments from people who've hit the same bug or whatever.

FYI, I have no problem with any other apps on this issue, only Adobe's CS6 under Lion 10.7.

Chris, have you read all of the above posts? Many people are saying this only happens with Adobe and some are not using ML.

I use all of those programs, but only have the cursor problem with Adobe.

22 years using Macs and developing softs. No cursor issues any other aps but Adobe since ML upgrade two weeks ago....

Weird, but I've been using those apps everyday since the day ML came out and have yet to encounter cursor disappearance.

Chrome, Safari, iTunes, Office, ...

See https://discussions.apple.com/thread/...
http://www.maclife.com/article/featur...
http://www.ibtimes.com/mac-os-x-mount...

Chris, could you name at least one more of those "multiple" applications this happens in?

We don't know what changed exactly, other than using more GPU features. Apple will have to tell us that once they have the cause of the bug identified.

We're not allowed to share RADAR information per NDA with Apple, and you wouldn't have access to the bug anyway (right now even I don't have access, it's in Apple's court).

Unfortunately, our outsourced support personnel are not always up to date.

Ray - sorry for the grammar snafu, I'll go fix that.
And I'm not a support employee, I'm a senior engineer writing Photoshop. I just answer customer questions while waiting on other things (like compiles, or an IDE to relaunch after yet another crash due to bugs in the debugger).

This happens in multiple applications, and is due to a known bug in the MacOS software. There is nothing we can do to work around it, and we, like you, must wait for Apple to fix the bugs in Apple's software. We have contacted Apple, but we cannot make Apple fix their (many) bugs. If you have some way to make Apple fix their bugs faster, we'd love to hear it. But so far the best known method to make Apple pay attention to bugs is for end users to tell Apple that the bug is important and that the users would like Apple to fix it soon.

This is happening with ADOBE software. It IS ADOBE's problem. If your software isn't working correctly YOU need to contact Apple and insist they fix the bug. This should NOT be an end-user's problem to solve.