interesting
/
libui
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Forgot something

This commit is contained in:
Pietro Gagliardi 2019-04-12 22:05:21 -04:00
parent 541f9d892d
commit 745f2da3b8
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/init-main.md
View File

@ -12,7 +12,7 @@ Furthermore, on some systems, this thread must also be the thread that `main()`
`uiInit()` *can* fail, in which case libui is not safe to use. `uiInit()` will return a human-readable error message to the caller if it does fail. You are also responsible for both allocating and initializing the memory for this error message, since part of libui's initialization includes initialization of its memory allocators. The reference entry below has more information.
Here is an example of a correct use of `uiInit()`:
Here is an example of correct use of `uiInit()`:
```c
uiInitError err;
@ -25,6 +25,8 @@ if (!uiInit(NULL, &err)) {
}
```
Note that if `libui` fails, you **cannot** use libui's message box functions to report the error.
## Reference
### `uiInit()`