Programming/Nesting Order ???

[skimask]

My main question: Is there a 'preferred order' to layout programming code/loops/nesting within nests etc.

Yep...Your Order. You're the programmer. The order is up to you.

For example, i might have a 16x2 LCD, a few buttons (or keypad), a few leds, switches or rotary encoder and/or a few external lines to the outside world.

In my mind, the user comes first, everything else is secondary. You get stuck in a loop checking buttons and the LCD won't update and the user probably doesn't get any feedback that your button press has been recognized. Find something to make some feedback, blink the backlight on the LCD, blink an LED, add a small speaker and make it beep.

I know someone will say "use an interupt" but i haven't got that deep into using interupts yet...

It's the only way to go... Play with them. They're easier than you think...

[gtvmarty]

Thanx for the info so far guys....

I've since found (well hidden) in the back of the PB manual that i should be using for..next loops for delays instead of "pause 1000", otherwise i need to wait for the 1sec to elapse before my key's are read in etc (obviously missing keystrokes during that 1 second).
That's a MAJOR part of my problem solved.

Yep, i had been thru all the "flashing-LCD-by-writing-too-often-in-a-loop" problems ;-)


I'm still not keen on interupts ;-) but am finding (with lotsa fiddling) that i can nest loops within loops nicely now, and i do have priorities to loop more often for keys than LCD writes etc.

Thanx again,
Marty.