00:13 < bridge> [teeworlds] <Dune> You could use the information from the previous frame and have a 1 bad frame
00:13 < bridge> [teeworlds] <Dune> But this looks like a bad idea overall
00:13 < bridge> [teeworlds] <Dune> Proper way would be to buffer all textinput and print it at the end I guess
00:14 < bridge> [teeworlds] <Dune> Hoping no quad needs to be on top of it
09:07 < bridge> [teeworlds] <heinrich5991> Learath2: this is a problem with immediate mode GUI
09:07 < bridge> [teeworlds] <heinrich5991> the layout is always one frame behind
09:29 < Learath2> Dune: SDL needs to know that we are doing textinput, before the input is processed
09:42 < bridge> [teeworlds] <heinrich5991> `CDataFileWriter::Open` returns true for success and false for failure, vice versa for `CDataFileWriter::Close`. opinions about the better way? @Learath2 maybe?
09:43 < Learath2> I think true for success is way more common in teeworlds code, except for system.h which follows the classic 0 for success
09:45 < bridge> [teeworlds] <heinrich5991> so `Close` will get true for success, ty
10:22 < bridge> [teeworlds] <heinrich5991> Learath2: here's what I meant with `NET_CTRLMSG_ACCEPT` and the datafile sizes
10:22 < bridge> [teeworlds] <heinrich5991> https://github.com/teeworlds/teeworlds/pull/2537