* Updated examples/Makefile after testing on OSX
I may be wrong, but the best way to install ray lib is through home-brew, and I'd expect that that should be a search path for others.
* Update Makefile
Fixed issues
* Fix borderless fullscreen always on top
Don't pass a monitor to glfwSetWindowMonitor(). This avoids setting the flag which keeps the window always on top.
* Update for borderless-windowed always on top bug
Only apply the fix for Windows OS, since that seems to be the only
platform with the issue.
* Update GLFW to 3.5.1
* Remove cocoa_time.c from rglfw.c
* Add macos_time.c to rglfw.c
* Redo changes from pull request #3863
* Makefile: add QuartzCore framework when building for macOS
* Add QuartzCore when building for macOS to other build files
* Remove unused GLFW dependencies
GetPoseAtTimeGLTF searches for the interval containing the requested time
with (tstart <= time) && (time < tend). A time equal to the last keyframe
satisfies no interval, so the loop ends without a match and keyframe stays
at its 0 default, making the function return a pose from the beginning of
the animation.
LoadModelAnimationsGLTF samples at t = j/60 for j in [0, keyframeCount),
with keyframeCount = (int)(duration*60) + 1, so the last sample lands
exactly on the end of the animation whenever duration*60 is a whole
number. The last pose of those clips is wrong, which looks like a jerk
right before the animation ends.
Measured on a glTF with a 0.85 s clip: the delta between the last two
poses was 23x the median delta between consecutive poses; with this
change it is 0.3x, in line with every other step.
* [examples] Add core_scissor_shape
Clip drawing to an arbitrary shape using the stencil buffer, since
BeginScissorMode() only supports axis-aligned rectangles.
* [examples] Rename to gl_scissor_shapes.c
Rename core_scissor_shape to gl_scissor_shapes, move to others. Per @raysan5's review feedback on the PR: keep OpenGL-facing examples
under examples/others, consistent with rlgl_standalone and
raylib_opengl_interop, to avoid multi-platform/build-system issues.
* [rshapes] Fix drawing circle sectors
Functions that draw a sector of a circle would keep drawing segments past a full rotation, which looked bad.
* [rshapes] Change `DrawCircleSectorLines()` and `DrawRingLines()`
`DrawCircleSectorLines()` and `DrawRingLines()` drew the cap lines even when drawing a full circle, which seems undesirable.
On Android (AAudio) the callback thread could still run when the mutex was
destroyed, causing a SIGABRT (pthread_mutex_lock on a destroyed mutex).
Uninit the device first so its callback thread stops before ma_mutex_uninit.
When the activity is destroyed while the app is paused, PollInputEvents
kept looping after setting CORE.Window.shouldClose: while paused,
ALooper_pollAll is called with an infinite timeout (-1), so on the next
iteration it blocked forever waiting for an event that never arrives.
main() never returned, the native thread stayed alive, and the following
launch hung inheriting that thread.
* [rshapes] Update `DrawRectangleLinesEx()`
Add support for negative `thick` values. When `thick` is negative, lines are drawn growing outside of the rectangle.
* [rshapes] Update `DrawPolyLinesEx()`
Add support for negative `thick` values. When `thick` is negative, lines are drawn growing outside of the polygon. Also refactored to explicitly use an `outerRadius` variable instead of using `radius` as the outer radius.
* [rshapes] Update `DrawRectangleRoundedLinesEx()`
Make the outline vertices easier to work with.
* [rshapes] Updated `DrawRectangleRoundedLinesEx()`.
Lines used to draw outside when `thick` was positive. Added support for negative `thick` values. When `thick` is negative, lines are drawn growing outside of the rectangle.
* [rshapes] Update `DrawRectangleRoundedLines()`.
Make the formatting of the points' x and y coordinates in DrawRectangleRoundedLines() match DrawRectangleRoundedLinesEx().
NOTE: raylib data validation policy defines not to validate any data that does not suppose a crash in the program, letting user manage that layer... probably several functions should be carefully reviewed or the policy itself...
