Aaron Franke
7d64830cfe
Ensure most demos have descriptions and screenshots
|
3 lat temu | |
|---|---|---|
| .. | ||
| screenshots | 4 lat temu | |
| MonoTest.cs | 4 lat temu | |
| Operating System Testing.csproj | 3 lat temu | |
| Operating System Testing.sln | 4 lat temu | |
| README.md | 4 lat temu | |
| actions.gd | 4 lat temu | |
| icon.png | 4 lat temu | |
| icon.png.import | 4 lat temu | |
| noto_sans_ui_bold.ttf | 4 lat temu | |
| noto_sans_ui_regular.ttf | 4 lat temu | |
| os_test.gd | 3 lat temu | |
| os_test.tscn | 3 lat temu | |
| project.godot | 3 lat temu | |
README.md
Operating System Testing
This demo showcases various OS-specific features in Godot. It can be used to test Godot while porting it to a new platform or to check for regressions.
In a nutshell, this demo shows how you can get information from the operating system, or interact with the operating system.
Language: GDScript and some C# (Mono is NOT required to run this demo)
Renderer: GLES 2
Check out this demo on the asset library: https://godotengine.org/asset-library/asset/677
How does it work?
The OS
class provides an abstraction layer over the platform-dependent code.
OS wraps the most common functionality to communicate with the host
operating system, such as the clipboard, video driver, date and time,
timers, environment variables, execution of binaries, command line, etc.
The buttons are connected to a node with the actions.gd script, which
perform actions using the OS class.
The text on the left is filled in using the os_test.gd script,
which gathers information about the OS using the OS class.
On a Mono-enabled version of Godot, Godot will load MonoTest.cs into
the MonoTest node. Then, information determined by
C# preprocessor defines
will be added to the left panel.
Screenshots
