Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Name fields are weird #12

Open
3 of 5 tasks
kg583 opened this issue Jun 3, 2023 · 0 comments
Open
3 of 5 tasks

Name fields are weird #12

kg583 opened this issue Jun 3, 2023 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@kg583
Copy link
Member

kg583 commented Jun 3, 2023

The interpretation of the name field varies heavily with the entry type. It is "most often" best to think of the name as a single token, and if not that then a font string, though there are exceptions:

  • For lists (001h and 00Dh), if the second byte is <6 it tokenizes it, if 040h it prints "IDList", else it just uses the font for up to 5 chars.
  • For programs, appvars, and groups (005h, 006h, 015h, and 017h), it displays a font cstr of up to 8 chars.
  • For Window settings (00Fh, 010h, and 011h), it displays a hardcoded string "Window", "RclWindow", or "TblSet" respectively (or a localized string)
  • And Images (01Ah), it tokenizes 0EF50h + [byte two].

(summarized by @LogicalJoe following lots of reverse engineering)

The lib currently treats every name as tokenized, which agrees with the font and some of the special cases for the most part but begins to fail for things like GDBs.

  • Lists tokenize for L1 - L6, have "IDList" for some reason, and then use the font otherwise (up to 5)
  • Programs, appvars, and groups use the font (up to 8)
  • Settings types use hardcoded strings
  • Images tokenize the first two bytes
  • Everything else tokenizes the first byte (new default)
@kg583 kg583 added the bug Something isn't working label Jun 3, 2023
@kg583 kg583 added this to the Release 1.0 milestone Jun 3, 2023
@kg583 kg583 self-assigned this Jun 3, 2023
@kg583 kg583 pinned this issue Jun 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant