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

export not getting names right #1

Closed
biffhero opened this issue Nov 28, 2020 · 5 comments
Closed

export not getting names right #1

biffhero opened this issue Nov 28, 2020 · 5 comments

Comments

@biffhero
Copy link
Owner

In the Open dialog in MC, the name is EE.GetListID.

In the XML file, the line is

	<data first="fa_EEa2eGetListID" second="0"/>

In the functions/ directory, the file is called _EEa2eGetListID

This should be called EE.GetListID

@biffhero
Copy link
Owner Author

biffhero commented Nov 29, 2020

This is not a case of "a2e" needing to become ".".

This is a case of "how to encode special characters in names?"

Here are the rules I'm going to go with.

  1. The first section is the rules. This goes up until the first _ character.
  2. Within the first section, the first character is the 'file type'. f, function. i, indicator. s, signal.
  3. Within the first section, the second character is the 'special character delimiter'. This character is the character within the file name that precedes any special characters in the file name.
    For example : fa_EEa2eGetListID would mean 'a' is the offset, and '2e' is the special character, which is translated to a '.'.
  4. _ character. This first underscore is the delimiter between the rules and the names. So if your name starts with two underscores, the xml file will have three underscores in it.
  5. The name of the file, with the special characters and the delimiters in them.

I have seen delimiter characters from a-e, and special characters in the set of [20, 2e, 2d, 24, 25], which correspond to the values "space", ".", "-", and two others that I can't figure out by just glancing at it.

I am guessing that this is something done to accommodate all sorts of characters in the file names. Therefore, I'm going to put a fail-safe mechanism in the decoding function, so that if a new character shows up that we don't know about, we will exit the application. There will be a command line switch to continue, however.

@biffhero
Copy link
Owner Author

mcexport

@biffhero
Copy link
Owner Author

image

@biffhero
Copy link
Owner Author

image

@biffhero
Copy link
Owner Author

image

@biffhero biffhero changed the title function export not getting everything right export not getting names right Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant