Late last month, some Adobe Photoshop users reported that the new 2013-edition MacBook Air was exhibiting severe flickering when using some brush tools in Photoshop.
It didn't happen with all units, but an Adobe representative said he believed it was a driver or GPU issue, and said Apple would need to fix the issue.
Today, a MacRumors tipster tells us the flickering issue has been fixed in the OS X 10.8.5 beta released to developers today. The bug made Photoshop nearly unusable for a number of MacBook Air users.
Some users have previously suggested that upgrading to the developer release of OS X Mavericks solved the problem, so the fix may be a matter of Apple pushing upgraded code sooner than it planned.
(Thanks, Todd!)
Top Rated Comments
It's an ADOBE bug, not an Apple bug. Makes me sick that Apple would have to stoop to Adobe's level and fix THEIR bug.
Can you please explain why this is Adobe's Bug ? Seems to me it's an Apple Problem..:apple::apple::apple:
Explain yourself. Help me understand... How do you know that this is Adobe's bug?
I'll explain, a true fan must NEVER see wrong in their 'team' or favourite company, therefore its always everyone else's fault, hence the ':apple::apple::apple:' ...
It's an ADOBE bug, not an Apple bug. Makes me sick that Apple would have to stoop to Adobe's level and fix THEIR bug.
:apple::apple::apple:
Lol here go the fanboys haha, makes him sick? how would he even know who's bug it is, he must be working in the Adobe coding team and already figured it out :rolleyes:
It's an ADOBE bug, not an Apple bug. Makes me sick that Apple would have to stoop to Adobe's level and fix THEIR bug.
:apple::apple::apple:
Hop off Apple's nuts for a bit :)
It's an ADOBE bug, not an Apple bug. Makes me sick that Apple would have to stoop to Adobe's level and fix THEIR bug.
:apple::apple::apple:
That doesn't make any sense.
It's an ADOBE bug, not an Apple bug. Makes me sick that Apple would have to stoop to Adobe's level and fix THEIR bug.
:apple::apple::apple:
Explain yourself. Help me understand... How do you know that this is Adobe's bug?