Reporting ...
You have to understand that, as each RosAsm user has his own way of doing things, really fully testing such a big Application like RosAsm, is not in reality really possible. Each time I add a new function or improve an old one; I cannot test all of the functionalities and all possible ways for doing each thing. So, even if, with time, RosAsm is turning less and less buggy, you should not be surprised when pointing out some malfunctioning implementation or even some hanging bug.
I cannot fix bugs I have never seen and never heard about, but, when a user reports a bug, it takes to me very rarely more than 2 minutes to fix it.
Reporting is contributing.
How to report malfunctions is simple enough.
If RosAsm hangs after a given succession of user actions that I can easily reproduce, just email me the list of actions.
If the hang is more complex (more randomly coming up), simply make a 'CopyOfRosAsm.exe', run RosAsm, Load 'CopyOfRosAsm.exe' (or reverse), click on [Run], and, then, when RosAsm Child version hangs, the mother version tells you exactly where and what. This way of reporting, with the hanging instruction pointed out, makes fixing it very easy.
Additional points:
See what is hanging (a DLL, the OS, or really RosAsm itself).
Verify, of course, that the hang is not entirely your fault (example, after loading a 1 mb Wave file in Resources, after calling a DLL function with a wrong number of parameters, and so on...).
When reporting, tell me what OS your are running (mainly: Win95/98/ME vs Win NT/2000/XP families).
If you report with the instruction pointed out, do not give me the line number (continuously changing). Paste the chunk of code with a mark upon the instruction.
~~~~~~~