Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

oPro's AddWindowField

0 views
Skip to first unread message

Stuart Cox

unread,
Oct 25, 2002, 3:30:34 PM10/25/02
to
I'm working to design an entry screen that is patterned after the
example code in wField2.pas that comes with oPro.

The idea is to have several text variables that get populated from the
command line, but, when checked for validity and fail, an entry screen
pops up and lets the user fix his foul ups.

A couple of the variables are file names. If the user picks existing
files (and they're not the same as each other), then processing starts
up and he gets the output.

If the files don't exist, they're the same as each other or other
things are wrong with them then I want to display the entry screen and
show an AddStringField and an AddWindowField with a opDir.DirListPtr
stuck to it.

I can do this fairly well using the example in wField2, but, since I
have 2 input files and limited screen realestate, I'd like to make
invisible the DirLists until the focus is in the AddStringField
associated with that field's partitular DirList.

opSelect's ChangeInvisibility method doesn't affect the DirList field.
I can't get either of them to disappear and so I can't position the
two of them on the same spot. Neither can I position them over other
fields that could be made invisible for the time that the file names
were being input/chosen by the user.

Is there a solution? Thanks in advance.

0 new messages