I was doing some work with native ODBC through the incredibly useful and excellent ODBC-wrapper Nanodbc. In theory, it should be simple work. However, when things can go wrong, they will go horribly wrong.
Primitives in C++ language can have signed and unsigned values. Signed means that they may be both positive and negative. Unsigned values may be only positive, but as a result may hold more values.
I am in the process of rewriting some software, and one of the steps is to replace an ancient ODBC client library with a more modern C++ SQL server wrapper client library.
I was working with a full width and height slider page for my new WordPress theme and it just didn’t want to give me 100% screen height. While on a desktop computer it would not matter, on mobile devices I wanted the slider to be as easy as swooping to the next page with a finger, just like in a book.
Recall our previous post about stretched terrain bug in the game. Shader that fixed the problem gave although an unpleasant bug in the form of many black dots with newer graphic drivers. The black dots are usually a result of a NAN error (not a number) and normally related to bad geometry, a bad shader, light or camera.
Recently I needed to fix a bug where a mx:TextArea was always dirty. The reason was a text with line breaks like:
I’ve recently come to an issue where I needed a ComboBox in Flex with dynamic dataProvider and couldn’t work it around for a while. There is a bug in SDK 3.5 so that a dropdown list in a combobox shows old values after change of dataProvider. To overcome a problem you need to bind the dataProvider.
