Examining the code shows that the rectangle is drawn winding counterclockwise, starting
with the top left. Therefore the colors used should be in the order: topLeft, bottomLeft,
bottomRight, topRight.

However, the variables actually being used are topLeft, bottomLeft, topRight,
bottomRight. I was confused by this as I was getting striping where I didn't expect any.
Put another way, the last two parameters are misnamed.

This diff swaps the parameter names and their usages. The result is that no runtime
behaviour changes: the same parameter order yields the same visual result both before and
after this change, but the parameter names now correctly reflect what they are actually
used for.

You can actually see this in the implementation of DrawRectangleGradientV, which
(correctly) passes top, bottom, bottom, top to DrawRectangleGradientEx.

Update RGFW to 1.7.5-dev

RGFW: fix Escape always closing the window

Update RGFW to 1.7

[rshapes] Add DrawEllipseV and DrawEllipseLinesV

Update comments

Update comment (gamepad axes)

RGFW backend: add missing Right Control key

Remove unused variable

Found some issues with output size when padding required, just re-implemented both functions from scratch.

Note that returned output size considers the NULL terminator as an additional byte.

[rcore] Fixed bug in hovering and input for android

corrected coding conventions.

Fix typo in mesh animNormals

Bug Fix Update
Code to Ignore Hovering Inputs Completely

[examples] Basic pbr example fix

It is called on window minification and setting internal width/height to 0, that can break things

build.zig fixes for android targets

[rmodels] Fix and improve `GenMeshTangents`

[utils] fix const warning with SaveFileText callback

- All `char *` refer to text strings
- All `unsigned char *` refer to generic byte arrays