RNTester

red center glyph gets cut off

The Forge sounds pretty great but there does not seem to be much in the way of documentation.

I don't even see simple "How to compile" or build instructions. Which seems like a good place to start.

The description talks about it being like "Legos" where you can use the different parts of the system as needed. So does that mean it can be built in sections and integrated into other projects pi

Below, all pull request that are currently closed, with an indication on their status.

This overview should be kept up to date, to prevent uncertainty. Also, having this up to date overview avoids spending repeated efforts to ascertain the state of closed pull requests.

Possible states per pull request:

• Invalid (explain why it wasn't good)
• Obsolete (should reference replacement pull request

The gesture is not always recognised and touch is taken instead of quick pinch, which causes stroke creation on the canvas.
Refer the video of Paint 3D application: -
https://cl.ly/f048de28e322

Currently we initialize the SDL sub systems for xid-sdl.c on a per instance basis.

Following the guide written here: https://people.redhat.com/~thuth/blog/qemu/2018/09/10/instance-init-realize.html. We should only initialize the subsystems once using class init.

The dead zone range in the editors matches an 8bit axis. It is scaled internally according to the axis resolution of the emulated controller type.

The dead zone range in the editors should be adjusted according to the axis resolution of the emulated controller. For example the Xbox 360/One have 16bit axes for sticks.

Hi,

here is a YouTube Tutorial. You could embed it into the github readme.md if you like. This could help people a lot.

https://youtu.be/UEfqpKyDQ48

There are a few problems I think we can address:

• Info in the app is not available on the GitHub readme files, and vice versa.
• It should be easy to maintain parity of important information between the app's Info tab and the GitHub readme files. (Ideally without duplicating the info. Currently we have a multi-page informational document embedded inside a resource file in the app.)
• The inf

There are a lot of variables in hal/video.c which should be static.

https://github.com/XboxDev/nxdk/blob/ce8da0b9cf93a6ce0051a7a2399cfdb93771e6ea/lib/hal/video.c#L36-L42
https://github.com/XboxDev/nxdk/blob/ce8da0b9cf93a6ce0051a7a2399cfdb93771e6ea/lib/hal/video.c#L61-L62
https://github.com/XboxDev/nxdk/blob/ce8da0b9cf93a6ce0051a7a2399cfdb93771e6ea/lib/hal/video.c#L121

Some of this intera

Currently we have build instructions for macOS / Linux users but point Windows users to the AppVeyor builds.

This is great for the more common user, but if one is interested in developing/improving extract-iso it can be helpful to have build instructions.

Actual behaviour

The SoundOptionsScene are empty and also some other options are missing.

Expected behaviour

There should be options for the general volume and preview volume.
Note that at the moment there is no song preview (see #89) but the option can be prepared nonetheless.

It would also be nice to have some options for the SingScene. For example, debug options to enable

Need to find out if we should do this or not, it seems xvdd relies on the hash table when en/decrypting, but with our current code xvdtool doesn't actually require it, should we change this? Will have to check with xvdd & other official tools - we don't want to create files that nothing official can actually read.