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

SCANMSG only supports a modules own MSG files, not *ANY* MSG File #630

Open
enusbaum opened this issue Aug 9, 2024 · 0 comments
Open

SCANMSG only supports a modules own MSG files, not *ANY* MSG File #630

enusbaum opened this issue Aug 9, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@enusbaum
Copy link
Member

enusbaum commented Aug 9, 2024

Documentation from Dev Guide:

image

Our current implementation only supports the MSG files defined in the module MDF file.

The scanmsg implementation needs to be updated to:

  • Search the current module path for an MCV file of the same name
  • If not, create a new MsgFile object, and compile a new McvFile
  • From the McvFile object, load the specified value

Because MBBSEmu modules can exist in their own folders/paths, we'll need logging if a specified MSG file isn't found, since the end user will need to ensure that the dependent modules are loaded with one another.

@enusbaum enusbaum added the bug Something isn't working label Aug 9, 2024
@enusbaum enusbaum self-assigned this Aug 9, 2024
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