You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I've been planning to implement GetMonitorWidth and Height for android
the seemingly most convenient way to implement it would be using the getSize method of Display, since displays are the closest thing to monitors
pretty much all of the display based size methods were however deprected with api level 30 and replaced with the newly introduced WindowMetrics api, which also doesn't map to the idea of monitors nearly as nicely.
Personally I would just stick to the old api, since it's nicer, but that obviously wouldn't work long term.
Which raises the question of how raylib should deal with android api levels.
I know that raylib already has some means of dealing with different OpenGL versions. Maybe this should be dealt with in a similar manner? I dont know.
To me this issue seems annoying to deal with and like a big hurdle if we ever want a complete implementation of rcore_android.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So I've been planning to implement GetMonitorWidth and Height for android
the seemingly most convenient way to implement it would be using the getSize method of Display, since displays are the closest thing to monitors
pretty much all of the display based size methods were however deprected with api level 30 and replaced with the newly introduced WindowMetrics api, which also doesn't map to the idea of monitors nearly as nicely.
Personally I would just stick to the old api, since it's nicer, but that obviously wouldn't work long term.
Which raises the question of how raylib should deal with android api levels.
I know that raylib already has some means of dealing with different OpenGL versions. Maybe this should be dealt with in a similar manner? I dont know.
To me this issue seems annoying to deal with and like a big hurdle if we ever want a complete implementation of rcore_android.
Beta Was this translation helpful? Give feedback.
All reactions