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.
Dear Chris Cox,
I see that you missed reading my earlier posts in this thread, and you seem to have skipped a lot of other user's posts as well. If you look back you will find that not only did I report using a Mobile Intel 945 Express graphics chip (so you can't blame ATI there), but I also found evidence suggesting that Photoshop CS2 does indeed hijack the ESC key: By pressing ESC in a different application I was able to cancel the loading of a large image in Photoshop. Please explain this in terms of "it's not our fault, blame so and so..."
Others have reported similar issues with other graphics cards still, many users having NVIDIA graphics cards and drivers - and you still claim it's ATI's fault? Even though killing the process of the respective graphics card's control center, or deleting the plugins folders, or turning off UAC seems to alleviate the problem in some circumstances, the one common denominator in all reported cases is... Photoshop!
You should be careful not to utter ridiculous statements like "sorry that you continue to blame the wrong party", when in fact you seem to be doing just that. It's evident that you are not on the Adobe marketing team, or you would probably know better and choose your wording more carefully. Please remember that most customers writing here are not media trained, but rather just frustrated users. You, on the other hand, represent Adobe and should really not be the one taking this discussion to the sandbox level. Perhaps some basic training on marketing and customer communication would be in place if you are to continue participating in these forums? I just took the time to re-read this entire thread and not anywhere did I see the "Thanks for bringing this issue to our attention, we take your concerns seriously and will go to great effort to find a solution to this problem which seem to cause a great deal of aggravation to our valued customers" response one could expect from a reputed software company. Instead all your responses seem to be trying to blame someone else. It's so unprofessional - and immature - it leaves me flabbergasted.
I do recognize that computer systems of today are incredibly complex, with a myriad of potentially conflicting software running simultaneously, there is a slim chance that Photoshop is not actually the culprit here. But let's face it - at this point there is no strong evidence that suggests that. Rather, since Adobe's official attitude has always been "its' probably not our fault..." it's way too likely that your next (silent) thought was "...so we're not even going to look into it with a great deal of effort".
It just goes to show what Adobe really stands for, and frankly - it leaves me quite disappointed.
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.
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.
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.
Ok, but what about this then:
- Brand new install of Windows 7 Professional x64 nl_NL
- Only nVidia WHQL latest drivers (no control panel).
- Installed all Windows Updates that were offered
- Installed all the Adobe updates that were offered.
Esc key still not working in other applications when Photoshop CS4 is running!
For the love of sanity, at least admit there could be a possability that this "feature" is'nt exclusively third party related, and I'm stating it very nice, I believe.
Unfortunately, it's all too late, CS5 upgrade is the only real sollution aparently and I can't afford it right now.
Intel chipset users should look at this post: http://forums.adobe.com/message/1636488#1636488 ricght-click on your intel GMA icon in the system tray , and check "disable hotkeys" OR in the intel drivers settings, uncheking rotate displays did the trick for the same user.
I am also having this problem, however, it is with a much larger problem in my specific case.
For nearly six(6) months now, I have been using Adobe Photoshop Elements 8 since I purchased the program with my Wacom Pen and Touch art tablet, and for a while the program worked fine. Recently, I have been having a recurring problem with the functions of my keyboard keys such as my 'esc', 'crtl', 'alt', 'Capslock', and even the function command keys either malfunctioning, being broken, and even switching command functions in a random pattern(ie. the 'Delete' key will become both Delete and F3/4/5 simultaneously.). This only happens when Photoshop Elements is running, and the problems only get worse when the Elements Editor is opened. I have attempted to perform the suggestions found in this forum topic, however the Shift+Esc command does not work for me when I use it. Again, this only happens when I am running Photoshop Elements.
As of late, I have been experiencing crashes in your software that are now beginning to delete my saved images. The deck for Elements 8 works fine, and I have not had any problems with the Organizer, aside from the breaking of certain key commands. However, when the Elements 8 Editor is opened, immediatly after initializing the UI the program crashes and deletes or corrupts any file I am trying to open. Recently I have started creating duplicates of my remaining PSD files because the program is corrupting PSD files at random apparently on my computer every time it crashes. I have already had a full system failure as a result to your software crashing.
I have never had this problem with any other software. This problem is isolated to Photoshop specifically, and is a software malfunction, apparently unrelated to any specific drivers and processors. I have been advised by others to 'upgrade' to a newer version of Photoshop, however to preempt this, my answer is the same as all others: I have limited funds, and I do not have the money to upgrade to a newer version of an already faulty software.
I rely on your software heavily right now as I am trying to get into school, and this unreliable software is creating a serious problem for me.
I run Photoshop Elements 8 on Windows 7 Starter with a 1.67Ghz Intel Atom processor and 2GB of RAM.
I would like a solution to this problem, not a patch, seeing as the most expensive photo-editing software on the market is quickly beginning to take up actions that I suspect are the work of a malicious program.
Adding another case to the list here....
I am running Photoshop CS3 on Vista 64 and just recently started having this same issue.
I am not sure what the exact change would have been, but it started happening less than a month ago.
...I close PS CS3 and the problem goes away.
I am already in the midst of upgradding my whole system, hardware and software to Win 7x64 and CS 5.5, so it is not a crisis for me. But as I live in Photoshop and Illustrator most of the time, a non functioning escape key is pretty frustrating. If I can help diagnose the problem, let me know.
Europe, Middle East and Africa