erabo/spiegel-keyman
1
0
Fork 0
mirror of https://github.com/keymanapp/keyman.git synced 2026-08-05 08:25:32 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10
spiegel-keyman/developer/docs/help/guides/develop/walkthrough/04-using-debugger.md
Marc Durdin c10a74cdf0 docs: feedback for walkthrough 
Presenting as a commit as I made many minor edits in-place and this was
much simpler than trying to use GitHub review for this level of detail.

Test-bot: skip
Build-bot: skip
2026-02-17 14:01:17 +01:00

2.3 KiB
Raw Blame History

Using the Debugger

Part 4 of the [Keyman Developer Walkthrough](.).

← Part 3 - Creating a Desktop Layout   Part 5 - Designing a Touch Layout →

Step-by-Step

  • From the Debug menu, select the Start Debugging menu item. Some extra fields will be shown.
  • Type ;. The Keystroke log will show ;. The display to the right has two sections. The upper section shows the characters displayed on the screen. The lower section shows a table of characters and their Unicode values. Here the upper section will show ; and the lower section will show ; and U+003B. (U+003B is the Unicode value for “;”.)
  • Type e. The Keystroke log will show ; and E. The display to the right will show ɛ in the upper section and ɛ and U+025B in the lower section. (U+025B is the Unicode value for “ɛ”.)
  • Type ; then E. The Keystroke log will show ; E ; Shift+E. The display to the right will show ɛƐ in the upper section and ɛ and U+025B then Ɛ and U+0190 in the lower section.

  • From the Debug menu, select the Stop Debugger menu item.
To continue the Step-by-Step tutorial move to the next page: [Part 5 - Designing a Touch Layout](05-designing-touch-layout)

Running the Debugger

See the debugger documentation for more information on running the debugger.

Interpreting Errors

When compiling your Keyman code, Keyman Developer will report any errors, warnings and hints in the box at the bottom of the window. The message will give a short description of what the compiler found was wrong along with the line number of where the problem was detected. The error, warning or hint has an identifier (“KM02033” for example). This identifier is a link to a more detailed description.

[← Part 3 - Creating a Desktop Layout](03-creating-desktop-layout)   [Part 5 - Designing a Touch Layout →](05-designing-touch-layout)