Copy link to clipboard
Copied
Copy link to clipboard
Copied
Tomas - I'm very sorry that you misread the posts in this topic and misunderstood most of what I've been saying. And I'm sorry if I did not use the precise words you were looking for when trying to help people figure out what was causing the problem on their systems (when so many other users don't see a similar problem).
If you read the forums more closely, you will find that we investigate reports of problems, acknowledge our own problems and get them fixed as soon as we can. But what's left after that are problems that we cannot fix, things outside of our control -- and that's what most customers run into after we fix our problems. So yes, many of the explanations are going to involve someone else's code - because that's the most common cause of problems (by a huge margin). That does not mean that Adobe, or I, always blames others - it's just simple process of elimination that the external causes are the majority that remains.
Copy link to clipboard
Copied
Chris, has ATI ever said why they might want to absorb Escape key presses for certain applications? Or did it just seem to be a bug in their Hotkeys implementation? Notably Hotkeys were not even enabled by default, at least not on my setup.
-Noel
Copy link to clipboard
Copied
We didn't get a response with any details, unfortunately.
We think it was just a bug.
Copy link to clipboard
Copied
Chris,
I have a brand new Sony Vaio laptop using an Nvidia GT 520M graphics card, and yet I am experiencing this exact problem with my Esc key. This clearly isn't an ATI issue in my case.
I'm using Windows 7 64-bit and Adobe Photoshop CS4 64-bit. If I close Photoshop normal Esc key functionality returns... that points to Photoshop as being related to the problem. You can try to shift the blame to other parties if you want, but you can't deny that the Esc key works perfectly when Photoshop isn't running.
Copy link to clipboard
Copied
Perhaps the upgrade to CS5 would be worth buying, if for no other reason than to just no longer be frustrated by this particular system integration bug. And it's not like Photoshop CS5 doesn't bring other value to the party. I couldn't live without Content Aware Fill. It's saved me countless hours of cloning.
While we hope that Adobe does the best they can to make their products work well on the most possible systems, the responsibility for making things from different vendors work on our systems is ultimately ours. This is the price we pay for inexpensive mix and match hardware and software. You may not think that Photoshop is inexpensive, but a few hundred dollars for a product that's a result of man-centuries of work is cheap indeed! And how much did you pay for your ATI video card, hardware, software, and all? Less than a hundred bucks I'll wager.
-Noel
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
ESC::
ifWinExist, ahk_class Photoshop
{
IfWinActive ahk_class Photoshop
{
SendInput {ESC}
} else {
SendInput +{ESC}
}
}
return
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied