awschult002
awschult002
@riri conditional compilation added. Where would be a good place to discuss whether or not this should be a default option?
This update still keeps with that ethos. Nuklear isn't tracking anything between separate `nk_begin` calls. Within the call, nuklear updates the draw buffer. so its holding all of the information...
also. let me know if I am coming off as too combative. I can get passionate sometimes. Ultimately, this is your project, not mine. I will concede to your will...
The CRC Table definition should be guarded by the `NK_DRAW_BUFFER_CRC`, so if it is disabled, that shouldn't get compiled in.
but you are right, this is not thread safe and i will make the update to move it.
i am trying to update to use the `struct nk_command_buffer` however, i am having a little trouble understanding where in the `nk_context` the command buffer resides? at the moment, a...
> But i don't see where the `overlay` gets cleared. Also... is `memory` where the draw commands are stored?? i found that you `memset` the overlay to `0` later in...
Version number bumped (i think i did it right). PR should be good to go.
PR is not good. Turns out that I don't understand how to work with the buffer system
I am asking for some help in figuring out a couple of bugs. When I try to run an example, I get Seg fault because the CRC read function gets...