The LA Fox Developer Newsletter

May 1994

Hot Tip....

Multiple Size Radio Buttons

by Gary Farkas

fEd. Note: The following article originally appeared

in FoxSpeak, the newsletter of the Capital District

FoxPro Users Group in Albany, NY. It is being

reprinted here from the May ‘94 issue of

DevNotes, the newsletter of the Milwaukee Asso-

ciation of FoxPro Developers.]

As you use the Screen Builder, some objects will

have properties that may annoy you. For example,

all radio buttons must be the same width, and all

must be in the same row or column. If you had a

series of radio buttons, you may be able to fit them

on the screen better if you could arrange each

button individually. Also, when you select a button,

the cursor will move to the next object after all of

the buttons.

The following procedure, used as a valid, will allow

you to make radio buttons work the way you want

them to. Then, define each radio button as an

independent object. In order to use this routine,

you need to select a prefix code for each set of

buttons. Define the three following variables:

where Prefix is your chosen prefix. For example, if

the prefix is LEVEL, the variables would be

LEVELANS, LEVELOBJ and LEVELLAST.

Initialize these fields as follows: PrefixANS with the

default value, PrefixLAST with the default field

name, and PrefixOBJ with objnum(&PrefixLAST).

Since you won’t know the object number, this

initialization needs to be in the SHOW snippet. As

you can see, it is best to choose a short prefix.

PrefixANS will hold your answer, PrefixOBJ the

previous object number, and PrefixLAST the object

number.

Each button will then have the valid expression

R_BUTTON(Prefix, Button Number, Total # of

Buttons). For example, R_BUTTON(”LEVEL”, 3,

8).

It Can’t Get Any Easier.

We’ve come up with an easy way to submit articles to

the LA Fox Developer Newsletter one that has

been overlooked for a long time.

You can submit your articles to either Chuck Williams

(72330,2326) or Barry Lee (72723,3422) on

Compuserve.

These articles can be on any FoxPro-related topic,

whether it concerns a new technique you’ve discov-

ered, a certain development technique you may favor

over others, book reviews, etc.

The quality of this newsletter really depends on the

members that support it, not just read it. And I think

we’d all be surprised by the useful information that

could be circulated around the membership.

So....

How ‘bout it?

[Gary Farkas is President of the Capital District FoxPro

Users Group.]

Page 9