topic Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20 in Installation & update

ESCAPE "ESC" KEY NOT WORKING IN AC 20

toofuerte — Fri, 08 Jul 2016 20:39:08 GMT

We recently started using the AC 20 and the esc key is not working to deselect or cancel actions. In other threads they talk about Photoshop or other program causing issues, or restart computer or just AC. However AC 19 works fine. The problem is intermittent every once and a while it does work.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Eduardo Rolon — Fri, 08 Jul 2016 20:51:27 GMT

It works here.
If you migrated your W/E from 19 try using one of the predefined ones to check.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

toofuerte — Fri, 08 Jul 2016 22:11:35 GMT

I tried resetting my w/e to default and still have the problem.

Thank You!

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Anonymous — Thu, 14 Jul 2016 19:25:01 GMT

I did not import my work environment (I never do because of problems like this), but am still have the problem of the escape key not functioning to cancel commands or deselect objects.

It is VERY frustrating trying to work like this. I use the escape key a lot.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Barry Kelly — Fri, 15 Jul 2016 01:11:31 GMT

The ESC shortcut is non-customisable so it shouldn't be affected by the Work Environment.

It is working fine for me but I only have the pre-release version and Windows 7.

I would be guessing there is some other program (or a Windows setting - but I have no idea what) that is blocking the ESC key.
Does it work in other programs.
Do you have an older version of Archicad - is it only 20 that has the problem?
If so then I would be guessing it is an Archicad 20 issue.
Can you start Windows in safe mode and then run Archicad to see if it works then?

Barry.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Erwin Edel — Fri, 15 Jul 2016 07:25:30 GMT

I once was convinced software was giving problems with my CTRL key, even convinced it was only occurring in that software, turned out the keyboard was breaking up after 10+ years of use.

Just saying, don't rule out hardware failure

If you have a spare keyboard laying about, try that for half a day.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Anonymous — Fri, 15 Jul 2016 14:40:43 GMT

Barry wrote:
The ESC shortcut is non-customisable so it shouldn't be affected by the Work Environment.

It is working fine for me but I only have the pre-release version and Windows 7.

I would be guessing there is some other program (or a Windows setting - but I have no idea what) that is blocking the ESC key.
Does it work in other programs.
Do you have an older version of Archicad - is it only 20 that has the problem?
If so then I would be guessing it is an Archicad 20 issue.
Can you start Windows in safe mode and then run Archicad to see if it works then?

Barry.

I replaced my keyboard about a month ago, because I do admittedly wear out my escape key and space bar. Same with my mouse, I wear out the scroll wheel and have to replace it every 4 to 6 months.

However, I just ran a test and it works in every other program, including older versions of ArchiCAD. It works to close an email in Outlook. It works to deselect in AutoCAD. It works to deselect / cancel in Archicad 18 & 19.

The problem is just ArchiCAD 20.

Thanks for your troubleshooting help, but this seems to be a problem with ArchiCAD or a compatibility problem with ArchiCAD 20 and ... something else. But not with any other program on my computer that uses the escape key.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Stephen Dolbee — Fri, 15 Jul 2016 15:30:01 GMT

So far, it looks like only those on Windows 10 are affected.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

toofuerte — Fri, 15 Jul 2016 16:40:25 GMT

Hopefully we can get some help from Graphisoft with fixing the problem. I do see that the only ones who are having thee problem are those using Win 10 and AC 20.
We have tried the things suggested to try and find the issue. In an old thread people had problems with Photoshop hijacking the escape key, however I haven't had it open and have restarted several times since I had it open. the other thing is we have other people in the same office that have the same thing and they are set up similar to me, Win 10 and AC 20.

Thanks all for the help, hopefully we can get this resolved quickly.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Karl Ottenstein — Fri, 15 Jul 2016 21:22:36 GMT

Not a solution... but does shift-Esc work for you as a temporary workaround?

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Anonymous — Wed, 20 Jul 2016 14:45:43 GMT

Karl wrote:
Not a solution... but does shift-Esc work for you as a temporary workaround?

I just tested this. Sadly, no, it does not do anything.

Well, it forces certain actions to orthos by pushing shift, but continues to ignore the escape key.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

toofuerte — Mon, 25 Jul 2016 19:00:13 GMT

Karl wrote:
Not a solution... but does shift-Esc work for you as a temporary workaround?

Sorry Karl it doesn't work.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Anonymous — Fri, 05 Aug 2016 12:07:12 GMT

Hi Guys,

i have the same problem.
I paste my post open today morning here:

pasted post:

"
We have a problem with the Esc. Fct. with the teamwork project in Archicad 20.
When i start using a function like translation or another, is it impossible to use Esc key for cancelling function.
The only possibility is right click -> cancel.

The most strange in this story is that i have realised some test.

xxx.pln -> the ECHAP function work correclty
xxx.pln sharing in bim server -> don't work correclty
bim server extract projet to place xxx.pln on desktop -> work correclty again

few test later, i'm sure that the problem is when the project is shared in the bim server. Hope GRAPHISOFT will make a patch for this problem.

the Esc function doesn't work only when a fct is launched.
so

if i select a line fort exemple.
I use ESC -> unselect so it's ok.

if i select a line, i launch the translation. but "oh finaly i don't want to do it" Wink
Esc don't work

Tips: when i'm in a translation for example, Esc. is not working fort cancelling my function, i do a zoom in or zoom out and Esc is useable again.
SOOOOOO STRAAANNNNGE....

I'm working in a group of 11 person and all of them have the same problem. (only with AC20 - AC19 no problem)
"

ESC key not working...

rgarand — Fri, 12 Aug 2016 16:43:50 GMT

Is anyone else having a problem with the ESC key not working as intended? I have ALWAYS used my ESC key to get out of a command & deselect an object.

Lately if I have an object selected and I have NOT started a command, it will deselect as expected, BUT if I am in a command and try to cancel out of it/deselect the object, nothing happens.

Just wondering if it's just me...

Re: ESC key not working...

shtarkel — Sun, 14 Aug 2016 14:35:06 GMT

It's a bug

Re: ESC key not working...

rgarand — Mon, 15 Aug 2016 15:03:50 GMT

Lovely. I hope this is fixed before I get used to the work around.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Barry Kelly — Tue, 20 Sep 2016 02:30:30 GMT

I have just read in another forum that it seems to be a bug.
Seems to do with undocked palettes that have an active teamwork panel in them.

Solution is to try docking or closing the palettes of possibly just closing the teamwork panel in the palette.

Apparently the Favorites and Profile Manager palettes seem to be the main problems.

Barry.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Anonymous — Wed, 28 Sep 2016 01:22:35 GMT

So I have discovered the same problem and it only happens when i have bluebeam open simultaneously.

Jason

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Ernest Atanasiu — Tue, 11 Oct 2016 14:23:43 GMT

I can confirm that having the Profiles palette open is causing the bug to appear.
Teamwork environment on W7.

Re: ESCAPE "ESC" KEY NOT WORKING IN AC 20

Jeff Kogut — Mon, 17 Oct 2016 16:59:59 GMT

Suffering through this the last couple of days wondering what was randomly going on until I found this thread. Closing the profile manager fixed this on my Teamwork project in 20 / Win7 project.

I think this sort of bug is INSANE that the developers have not fixed it since it was reported in July, over 3 months ago. These usability bugs should have TOP PRIORITY imho and fixed within ONE WEEK.

Frequent updates = good. Fixed issues waiting months until a roll-up of fixes is ready = bad.