The Hints & Tips Page

Back

General Programming

1. When designing a new project sketch out your windows on paper, with a brief note about any buttons in the window.
2. When compiling software, think about using the RAM disc. It will save wear and tear on your harddisc.
3. Frequently save uncompiled code, so that if any changes are truely disastrous you won't lose weeks of work. Keep some form of hierarchy. For instance the first save is file1 the second file2 and so on. If you don't want hundreds of files keep circulating e.g. file1, file2, file3, file1, file2 etc... At the end of the session delete all the oldest files and keep a copy of the end of session file in a backup directory. It saves an awful lot of heartache.

WimpBasic Specific

1. Build up a library of basic items. For example the procedure that quits the application, frequently used windows etc.
2. When using the SYS command always use integer variables. Failing to do so can lead to some very obscure results, but usually not crashes. It can be very difficult to resolve.
3. If a window is used a lot within an application think about hiding the window rather than closing. You keep all the internal variables.
4. If you have a programming problem, run a second copy of WB and load a tutorial that carries out a similar function.
5. If all else fails go to the WB website, or make use of the WB mailing list.
6. If the problem remains unresolved contact Clares (but only as a last resort), they are very supportive.
7. If a command is not working as expected, fiddle around. A couple of commands as detailed in the online help and manual actually require a different format. (When I can remember which ones I'll post them here)

Back