We don't need to manage the IDs in the code. the ID's are only necessary during the loading process to make sure we rebuild the correct pointer relationships. Thus, the exporter should manage the creation of the IDs.
use gcdc and its affine transform
http://stackoverflow.com/questions/1761125/gcc-memory-leak-detection-equivalent-to-microsoft-crtdbg-h
in show text you always have to select the font
when an object has action and its image is edited it loses its actions (see objecteditdialog in OnOk() there we create a new action instead of editing the old)
replace whitespaces in strings with _
for example move area in another picture should place a flag where the area has moved to. then the on enter actions should respect these flags
when creating a game certain information should be given that do not change
- the possible acitons (talk to, go to, ...)
- the intentory style (MI1, MI2 static or MI3 right click popup or MI5 button open) and also the area where the intentory pops up
when no action is specified then a default action should be used
("no, I don't want to" "Not right now", and so on)