Food for thought: A browser accepts any HTML right, as insane as it gets and it will try to display something. These rules are written down in the standard of how to parse HTML. Does that mean that there is no possible way to write invalid HTML because there is always a recovery rule to fix your "mistake"?
for the free solutions we'll probably go with native rendering, a lot less of a hassle but will look different on each platform a bit
and then when we eventually get to QNX, we'll just have to bite the bullet and do the integration or write our own stuff instead of pango... apparently every project ever that has used it is ditching it for their own solution it's so crappy
Hmm got an interesting request. @lye am I right to assume that any sort of LFG api would need to be part of the chat-api style local communication? The guy asked for a compact lfg overlay that could be kept open to watch for stuff.
the compiler was throwing warnings at me earlier that there was some potential loss of data, because of casting of a bigger type to a smaller one; i, in good faith, added a preprocessor directive to have it set to a bigger type for 64-bit builds
apparently, there was some hardcoded stuff in my bitreader that only accounted for 32bit arrays
while the array was 64bit wide on 64bit builds, and the rest of the code happily assumed that there were actually 64bit numbers in there, while there actually weren't
they were just 32bit numbers stored in a 64bit array :D