Writing GUI sucks as usual, as opposed to pathfinding Posted: 2010.06.10

Recently I'm working on a university project: I'm supposed to code editor of heightmaps - I picked this topic because I think it's cool and allows me to get to know some new to me technologies (DX9) and concepts (graphics programming: modifiable heightmap, picking). Anyway, why I'm writing about this?

One of the tough decisions I had to face was choosing GUI tookit: WinForms, WPF, DXUT GUI, WinAPI, ..., or code my own? After some considerations I decided to try wxWidgets :] and immediately started looking on the internet for ways of embedding Direct3D context inside wxWidgets application, but to my disbelief, after a few hours I've found no ready-to-go code samples! Geez, one would think that such a popular and mature library like wxWidgets would have tons of examples on mixing it with currently most popular graphics API... unfortunately it's not true, and in great pains I had to combine together various pieces of code found on inet, to make it all work.

Eventually I made it: simple windowed application that can be resized, which embeds D3D context on which colored triangle is rendered; there's also a button which changes color of the background behind triangle as an example of UI code. In order to ease the life of other programmers, I release application's source code to public domain and you can get it at NoPaste. I hope my site will get better Google Pagerank so that more people can find and use this piece of code =) If you find it useful, please leave a note in comments.

As another university project (yep, again pretty busy academic year), I made simple A* implementation for path finding, in C++, using my homemade simple engine SC. It's finished and was positively reviewed, so I've added it to my projects list, where you can see screenshots, download (obviously exe + sources) and comment it :]

Also, make sure to checkout blog of my friends from Bionic Nose, who are very active indie game developers.

Last modified: 31.10.2011, 2847 days ago
Attention to detail counts. If you doubt that, consider that three of the most expensive software errors of all time -
costing $1.6 billion, $900 million, and $245 million ��� involved the change of a single character in a previously correct program