If I have a .cap and start changing conditions and actions from one object to another (like double clicking on the condition, clicking back twice, then selecting the new object and reselecting) then it isn't long before the GUI messes up and construct becomes completely unusable.
There was a GUI related memory leak i fixed a few weeks ago where closing the event wizard didn't free some gui stuff. I beleive this would have caused the GUI mess up and therefore I have fixed it. I'm changing this to pending incase you manage to reproduce this program again in 0.99.4.2 :)
Still in 99.42. It's the same bug as https://sourceforge.net/tracker/?func=detail&aid=2828735&group_id=207820&atid=1003219. I forgot to mention that on windows XP it results in an error "An invalid argument was encountered" repeatedly popping up. On vista the error doesn't appear, but construct is unusable in a very similar way, with many UI elements not being drawn. In previous versions I could still save - in .99.42 it crashes.
New clue: The bug occurred on the screen to enter the degrees for the 'set angle' action. On vista, after glitching out, parts of the windows taskbar turned grey. After reopening construct and redoing the 'set angle' action again, the taskbar redrew itself.
I'm not sure what it is, but since the windows taskbar didn't redraw itself until that screen, the bug's probably there somewhere.