The demise of the Escape key in favor of the Cancel button
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
14-12-21 01:53 PM
In version 6.5, where we are today, I can press the Escape key to cancel windows for properties for actions and parameters. You can also click the Cancel button but in many cases it is quicker to press Escape a number of times than looking for each Cancel button and clicking them. The Cancel buttons are by nature always on a different place on the screen and in my installation the cursor will not automatically be placed on the default button, in spite of my Windows settings dictating just that. So I have always been quite happy with the ability to press Escape instead of clicking Cancel.
While testing version 6.10, I noticed that some of the Cancel buttons no longer can be replaced by pressing the Escape key, instead, a real Cancel click is required to get back one step. I find the de-activation of the Escape key in BP6.10 highly annoying and not an improvement compared to our older version.
My questions:
While testing version 6.10, I noticed that some of the Cancel buttons no longer can be replaced by pressing the Escape key, instead, a real Cancel click is required to get back one step. I find the de-activation of the Escape key in BP6.10 highly annoying and not an improvement compared to our older version.
My questions:
- Is this altered behavior of the Escape key planned or accidental?
- If the latter: will it be improved upon?
- If the former: can you share the analysis that lead to this decision?
Happy coding!
Paul, Sweden
(By all means, do not mark this as the best answer!)
Paul, Sweden
(By all means, do not mark this as the best answer!)
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
17-12-21 12:34 PM
I doubt it was planned.... maybe raise with the support team that product hotkey behavior has mistakenly been removed by the Blue Prism product team with the newer release.
