-
Notifications
You must be signed in to change notification settings - Fork 25
Implement Mii Selector applet #78
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
Conversation
Also, out of curiosity, why is |
I've been researching, and the representation of the MiiData given by the 3DS doesn't change at all and is documented. The purpose of libctru's Instead of that, we could parse the raw data to a Rust-compatible struct. I'll do some testing |
(For some reason I can't request multiple reviews at the same time /shrug) |
- Make ``MiiSelectorReturn`` ``non_exhaustive`` - Remove ``checksum`` from ``MiiSelectorReturn`` - Change ``From`` impl for ``MiiSelectorReturn`` - Rename ``OriginConsole`` members - Fix ranges
Apply nightly lints I updated my toolchain to 1.66-nightly to fix all the files
I've squashed some commits (mostly docs and cargo fmt/clippy) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I meant to review this a while ago, but finally got a chance to take a look and it seems pretty cool!
Some of ctru::MiiData
might be worth documenting further, if we're going to maintain a totally separate struct vs the ctru_sys::MiiData
, but I think this is good to start. There's lots of documentation stuff that needs to be done across the board so I don't think it should keep this from merging as-is.
After current concerns about this PR are resolved, I plan on adding (at least) some basic documentation (and maybe references to the 3dbrew wiki) before merging, though I think the best thing would be to merge this PR with basic documentation and add more detailed documentation in a follow-up PR (I'm not a native English speaker, so I may need help in the follow-up PR, which may take some time to make because of that :p) |
Is there anything that should be documented in this PR instead of the follow-up? Or is this ready to merge? |
I believe it’s fine for now. PR anything you want to add. |
I've implemented the Mii Selector applet, I have yet to add documentation, but I would like to see your opinions on the API.
Specially around the creation and usage of the enums
MiiConfigIndex
andMiiType
.