So why is the display size not exposed to the user?

[keks137]

so I thought it was odd how screen size and render size are exposed to the user, but display size isn't,
since all three of these are printed during InitWindow()
and the display size seems quite useful to me to have, among other reasons, because to me it seems to conveniently abstract away the underlying hardware
so I made a PR recently #5188
which was understandably denied since I talked about it as a hackish solution to a platform-specific problem on android

but I do think CORE.Window.display has a lot of potential as an convenient abstraction for the underlying display size that already deals with a lot of platform quirks, so to me it just seems convenient to have

at this point it feels like I'm just missing something, so I'm really curious about why it is only used internally:
is it because it only gets set on initialization and isn't updated after,
or am I just misunderstanding the concept behind the display to begin with?

[maiconpintoabreu]

Display size should be the same as MonitorSize

INFO:     > Display size: 2560 x 1440 =  int GetMonitorWidth(int monitor); int GetMonitorHeight(int monitor);
INFO:     > Screen size:  2560 x 1440 = int GetScreenWidth(void); int GetScreenHeight(void);
INFO:     > Render size:  2226 x 1252 = int GetRenderWidth(void); int GetRenderHeight(void); 

[keks137]

well almost, on android for example it's ANativeWindow_getWidth(), which should usually return the same thing, but doesn't really refer to any hardware itself, but a surface within the software provided to you by the window manager
well maybe that difference isn't intentional, would have to look at other platforms as well

[maiconpintoabreu]

Maybe you could change the getmonitor size to return display on android as it is not used.

[raysan5]

raylib API tries to be common to all supported platform, despite the different naming conventions, for Android, "display" size should be the equivalent to "monitor" size.

[keks137]

ok makes sense, even if they are technically only logical displays, not physical ones, it should provide the expected functionality in pretty much all cases
also I don't think the android api even gives you info on the physical displays anyways

[keks137]

from the api refererce https://developer.android.com/reference/android/view/Display : A logical display does not necessarily represent a particular physical display device such as the internal display or an external display. The contents of a logical display may be presented on one or more physical displays according to the devices that are currently attached and whether mirroring has been enabled.

[maiconpintoabreu]

I don't know if it is public but you have this as well: https://github.com/raysan5/raylib/blob/master/src%2Fplatforms%2Frcore_android.c#L476

[keks137]

saw that, wonder if the inacurracies mentioned in the note are caused by the whole logical display situation
also should I just implement GetMonitorWidth the same way and just ignore the input, or is that only temporary?