Ray

Fixed... but still requires some work...

@Crydsch Excuse me for this super-late response, it's a big change and it requires time to review but I can't find the moment to jump into it... Taking a quick...

Not sure but this issue seems related to library versions mixing... latest raylib manages texturing in a different way than raylib 2.0...

Personally, I think it would be interesting to have the possibility to retrieve the ID3 chunk of data from the MP3 file, to allow processing it on user side. Just...

@carlsmith, just in case TCC doesn't work on Raspberry Pi and you still want to develop on that platform, you can take a look to [raylib](https://github.com/raysan5/raylib), it's similar to CToy...

Merged new camera redesign, reviewing it carefully in following commits...

@michaelfiber thank you very much for looking into this issue! :)

> And `/dev/input/mouse_` appears to be a legacy compatibility hack. I think so, it was originally implemented +8 years ago but many things have changed in this time... they can...

@michaelfiber Any progress on this issue? Afair, I used threads because mouse input was not updated fast enough when running headless but as I said, it was implemented long time...

@michaelfiber Sure! Take your time! Afaik, you are one of the users that has worked more extensively with raylib RPI to date!