Port 3ds-Example: graphics bitmap

[ian-h-chamberlain]

Ref #18

I modified the framebuffer API a bit since I don't think it makes sense to allow arbitrary Side for the bottom screen.

Also, the frame buffer returning a tuple (*mut u8, u16, u16) seems a little odd to me and maybe a struct would be preferable? Let me know what you think.

Finally – do we want to roughly match the directory structure of 3ds-examples? There are a lot of graphics examples and it might make sense to group them in a directory, as long as they still have unique names I think they are still easily runnable with cargo 3ds link --example $name. If so I can move this to a subdirectory.

Edit: screenshot! The colors on my device look a bit off, so I might try to play around with it to get a cleaner looking output... Also, for some reason, Luma screenshot isn't capturing the text on the top screen, but it is displayed there. Will investigate that.

[AzureMarker]

Also, the frame buffer returning a tuple (*mut u8, u16, u16) seems a little odd to me and maybe a struct would be preferable? Let me know what you think.

A struct would be nice, yeah.

Finally – do we want to roughly match the directory structure of 3ds-examples?

Cargo doesn't automatically infer examples unless they're in the examples directory (not a sub-directory):
https://users.rust-lang.org/t/run-examples-in-subfolders-using-cargo/18154/2

If there are examples with more than just one file though, they can be in sub folders with a main.rs.

[AzureMarker]

nit: Just a personal preference, but you don't need any of the local variable types in these functions. They get inferred from the return type.

[AzureMarker]

Luma screenshot isn't capturing the text on the top screen, but it is displayed there. Will investigate that.

I also found weird things with Luma and Console printing. It was just a black screen for me, like your top screen.

[Meziu]

Finally – do we want to roughly match the directory structure of 3ds-examples?

We can't make directories for examples. We can only group them by name (instead of a folder, put the folder name as a prefix to the file). It's not a big issue anyways.

[ian-h-chamberlain]

Cargo doesn't automatically infer examples unless they're in the examples directory (not a sub-directory):
https://users.rust-lang.org/t/run-examples-in-subfolders-using-cargo/18154/2

If there are examples with more than just one file though, they can be in sub folders with a main.rs.

We can't make directories for examples. We can only group them by name (instead of a folder, put the folder name as a prefix to the file). It's not a big issue anyways.

Ah, I forgot these details... I suppose if it gets out of hand we could make [[example]] entries in Cargo.toml, but for now I think this convention works.

---

New changes I'm pushing:

• Added a struct RawFrameBuffer

• Different conversion process for the image, which looks more correct. I guess the instructions from 3ds-examples were outdated. Note: it's hard to see if you use something like f.lux, which I had to turn off to notice a difference on my computer. On the device is more noticeable, although Luma filters might impact this the same way.

Screenshots

Before

After

---

I'll open a new issue for the Luma screenshot thing, since I think it might be something we can workaround on the ctru-rs side (I vaguely recall a code change I had which let me screenshot the console)