R
richard
http://1littleworld.net/button2.jpg
A screenshot of the buttons I created using Run Basic and the code
used to create them with.
for n=1 to 50
a$="do0"+str$(n)
b$=zp$(n,1)
button #a$,b$,[display]
#a$ CSSClass("stateButton")
print
next n
Can you imagine hand coding 50 links in html the old fashioned way?
CSSClass is how you change the look of the button.
Without it, you get the standard black lettering on gray background
button.
The # is a unique identifier for each item, not an ID as in the
styling of an item.
[display] is a label meaning "Go to this section".
Without the print, the buttons would naturally be floated side by
side.
The original array was preloaded and I tap the state names from that
array. The zip codes are in the same array and they will be printed in
the same manner in another division.
A screenshot of the buttons I created using Run Basic and the code
used to create them with.
for n=1 to 50
a$="do0"+str$(n)
b$=zp$(n,1)
button #a$,b$,[display]
#a$ CSSClass("stateButton")
next n
Can you imagine hand coding 50 links in html the old fashioned way?
CSSClass is how you change the look of the button.
Without it, you get the standard black lettering on gray background
button.
The # is a unique identifier for each item, not an ID as in the
styling of an item.
[display] is a label meaning "Go to this section".
Without the print, the buttons would naturally be floated side by
side.
The original array was preloaded and I tap the state names from that
array. The zip codes are in the same array and they will be printed in
the same manner in another division.