Hey! raylib forum is closing!
After a year with not much movement in the forum I decided to close it.
The cost of maintaining the hosting is a bit high for the usage of the platform, updating the forum and managing it is also a bit cumbersome and the truth is that I'm already trying to maintain multiple other networks pretty more active than this forum.
I'll recommend you to move to the other raylib networks:
- For a forum style, use Reddit: https://www.reddit.com/r/raylib/
- For direct messaging and questions, use Discord: https://discord.gg/VkzNHUE
- To report issues, use GitHub: https://github.com/raysan5/raylib
- Also, remember you can contact me personally on Twitter: https://twitter.com/raysan5
or directly by mail to ray[at]raylib.com
If you feel generous, you can also contribute to the project on my Patreon: https://www.patreon.com/raylib
Thanks to you all for joining the project and help to improve it with your questions. Keep it up! :)
PD. Closing will be effective by October 31th.
Looking for raylib ninja to help with project
I have a raspberry Pi0 project that I'm working on, using a 3.5" TFT display. I need to convert several older flash based animations into interactive raylib screens (because flash support on the pi is dismal).
The main issue using the flash animations is performance along and frame rate, especially when running in a resource heavy gnome desktop.
These animations are based on Star Trek LCARS interfaces.
I would like to create a sort of shell for these animations, using a signal from a GPIO pin (from a touch sensor) to toggle through the animation screens.
I have the flash animations, sounds etc, but most will more than likely need to be refactored completely into raylib assets. The only reuse would probably be the sounds and the outline of the screens.
If anyone has the time to take on a side project (no deadlines), let me know your rates/compensation requirements. I will also send along my project files for your review.