Update dynamic values in the Device context #20
Conversation
| @@ -73,6 +73,7 @@ Dictionary make_device_context(const Ref<RuntimeConfig> &p_runtime_config) { | |||
| device_context["model"] = model; | |||
| } | |||
|
|
|||
| // Note: Godot Engine doesn't support changing screen resolution. | |||
There was a problem hiding this comment.
Like, ever? How do Godot games support different screens?
There was a problem hiding this comment.
Godot doesn't change the physical resolution of your desktop environment, it changes resolution scale instead. I.e., projects 720p on 1080p resolution, for example, like consoles do. Most modern games do the same, some also support changing the real resolution. But this way it makes Alt-Tab faster, and fewer issues with it. Upscaling is cheap these days.
| device_context["free_memory"] = double(meminfo["free"]); | ||
| device_context["usable_memory"] = double(meminfo["available"]); | ||
|
|
||
| auto dir = DirAccess::open("user://"); |
There was a problem hiding this comment.
It's guaranteed to be writable, judging by the docs: https://docs.godotengine.org/en/stable/tutorials/io/data_paths.html#accessing-persistent-user-data-user
Also, some interesting bits:
On mobile platforms, this path is unique to the project and is not accessible by other applications for security reasons.
On HTML5 exports, user:// will refer to a virtual filesystem stored on the device via IndexedDB. (Interaction with the main filesystem can still be performed through the JavaScriptBridge singleton.)
The current default is to set context values during initialization, which works for most cases. The only context that is currently updated is "godot_performance".
This PR introduces a code path that updates values in the standard
Devicecontext just before the event is sent.Values that are dynamically updated in the Device context with this PR:
orientation,free_memory,usable_memory,free_storage.