OK. I understand now how you manage to process Tab as menu item shortcut. This results from

    switch (event) {
      case FL_FOCUS:
      case FL_UNFOCUS:
        return 1;

in your window's handle method. With that, the focus goes initially to the window object itself and Tab navigation is ineffective in that case, so the Tab keystroke is then analyzed as a candidate shortcut.

Source code changes for menu shortcuts to be displayed adequately under macOS (e.g., ⎋, ⌫, ⌦) and to be recognized correctly have been pushed to FLTK master and 1.3 branches. For your app to benefit from them, I'd advise to use the source code of the master branch which will soon become FLTK 1.4. It's likely there won't be another 1.3.x public release.

Please, close this issue if you agree it's fixed.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/issues/469/1197724470@github.com>