Page 2 of 2
Re: Text and 2D graphics window
Posted: Fri Mar 04, 2011 3:48 am
by spiral72
Yay, I sufficiently finished my list enough to code again.
Both routines work great! I added a 40ms delay between pixels and that's exactly what I want!
Now to dissect it to figure out what makes the code tick, then put it in my sonar program.
Y'all great. Thanks alot!
Re: Text and 2D graphics window
Posted: Sun Mar 06, 2011 8:56 pm
by spiral72
Ok, hopefully an intelligent question:
How are the ShowForm() and DrawArc() procedures any different from a GOSUB??
Re: Text and 2D graphics window
Posted: Sun Mar 06, 2011 10:17 pm
by IdeasVacuum
...its a very (very very) long time since I used a language that had a GOSUB function. Still, for all intents and purposes, the principle is the same. Subroutines and Procedures allow you to define your code in a logical way such that the code does not have to be executed sequentially from start to finish. For me, even if a Procedure will only ever be called once, it is still a good way to organise the code - effectively, a collection of 'mini programs'. I find it much easier to perfect several 'mini programs' than it is to work on one 'giant'. If a task is repeated, with perhaps a few values being changed, then a Procedure is the obvious way to go.