heeen

QString is a proper unicode-aware string with conversions to many character codecs. It doesn't really compare to std::string.

Except you don't have to pay anything if you don't plan to modify Qt itself, which you most likely don't need to do, and even then you just have to release the source to your modification to comply with LGPL.

It is actually more likely the rasterizer interpolated between values before running the fragment shader. This could be caused by the input mesh having an unexpected topology or some odd form of multisampling.

Why does this need a cookie to function? I block cookies by default and I get annoyed every time some site requires a cookie for something mundane like displaying the time or playing a game that doesn't even preserve state across browser sessions (like 2048)

edit: 2048 does indeed restore the game, but it should still work without a cookie.

Every client worth looking at allows rates to be adjusted, down to zero, if need be. Case in point http://screenshots.en.sftcdn.net/blog/en/2008/11/utorrent-3....

perl unicode support is actually pretty good http://dheeb.files.wordpress.com/2011/07/gbu.pdf

in this case, with only 5 planes and one sphere, you can pass the whole scene into the shader as uniforms. If you have arbitrary scenes, you can hack around this by estimating the water surface area where each triangle would be visible and then generate a water surface quadrilateral for each submerged triangle to raycast it. http://www.youtube.com/watch?v=oWrUvJYzRlQ