Open cmclark00 opened 1 month ago
No idea but I assume it's the environment. Does it happen with other SDL apps?
No, this is the only one. Weirdly it also happens with the old 32 bit dingux commander as well when I built it, but everybother sdl app seems fine
On Mon, Aug 5, 2024, 5:23 AM Gleb Mazovetskiy @.***> wrote:
No idea but I assume it's the environment. Does it happen with other SDL apps?
— Reply to this email directly, view it on GitHub https://github.com/od-contrib/commander/issues/25#issuecomment-2268591877, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3YSEJOE4CKWOT6WEPYFSP3ZP477TAVCNFSM6AAAAABL7QZKKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGU4TCOBXG4 . You are receiving this because you authored the thread.Message ID: @.***>
If you're using SDL1, try switching to SDL2
Hello, I have recently built commander for the Anbernic RG28/35/40XX series of devices. These devices are running on aarch64 linux kernel 4.9.170. for some reason when i launch the application i have to hit another button, like down on the dpad, or A on the gamepad or whatever, to get the application to display. I thought it may be something with my launcher script, but it does the same thing if i just run the application directly. I was wondering if you had any idea what might be causing this in our environment, because I can't figure it out. Thanks for taking the time to read this.