Comment 13 for bug 1092873

On 01/15/2013 03:30 AM, Jacobo Aragunde Pérez wrote:
> As JP said, this is only an issue with wxWidgets 2.8. I have been able
> to try it in Ubuntu with wx 2.9 and I couldn't reproduce the problem.
>
> I wonder if it's worth fixing what seems to be a bug in the framework
> and that has already been fixed.
>

From our project's file:

Documentation/guidelines/UIpolicies.txt

We read:

  Follow the recommendations here:
    http://library.gnome.org/devel/hig-book/2.20/windows-dialog.html.en
    paying particular attention to "initial focus", "sensible default values",
    "default buttons", ESC key termination. Please note that the escape key
    termination only works properly if there is a dialog button defined with
    an ID of wxID_CANCEL or SetEscapeID( MY_ESCAPE_BUTTON_ID ) is called during
    dialog initialization. The former is the preferred method for handling
    escape key dialog termination.

Sorry my memory is so bad. That's what folks with weak should memories do, write stuff down.

So indeed, the control ID is significant, as I merely guessedearlier. So perhaps some
dialogs can simply re-assigned a proper wxID_CANCEL or use made of the std button panels
which use this idon cancel button.

A third option is to use SetEscapeID() functionin dialog's constructor, per above.