Dave Crozier wrote:
... and "show get" (no s on the end) redisplays one object as opposed to the
whole screen
Dave
You also need the name of the variable after the show get E.g.
SHOW GET m.pn_vrn
Here's the full help text (From fox 2.6 windows)
SHOW GET Command
See Also
Redisplays the @ ... GET object that represents the specified memory
variable.
Syntax
SHOW GET <var>
[, <expN1> [PROMPT <expC>]]
[ENABLE | DISABLE]
[LEVEL <expN2>]
[COLOR SCHEME <expN3> | COLOR <color pair list>]
Remarks
Picture prompts are supported in FoxPro for Windows and FoxPro for
Macintosh.
SHOW GET redisplays a single control (a check box, field, invisible
button, push or radio button, list, popup, spinner or text-editing
region). When the value in
an @ ... GET field changes (the cursor moves to a new record, for
example), SHOW GET updates the value displayed in the @ ... GET field.
When a control
is redisplayed, it can be enabled or disabled. SHOW GET can also be
used to redisplay an individual button within a set of invisible, radio
or push buttons.
You can also change the prompts of check boxes and buttons with SHOW GET.
SHOW GET is typically used in a routine executed in a control-level
VALID or WHEN clause or a READ-level ACTIVATE or DEACTIVATE clause.
SHOW GET vs. SHOW GETS and SHOW OBJECT
Individual controls are redisplayed with SHOW GET or SHOW OBJECT. All
controls created with @ ... GET are redisplayed with SHOW GETS. SHOW
GETS executes the READ LEVEL SHOW routine. SHOW GET and SHOW OBJECT don't.
SHOW OBJECT is similar to SHOW GET except that SHOW OBJECT references
controls by their object number, and SHOW GET references controls by
<var>, the memory variable, array element or field specified when the
control is created.
For more information on control numbering, see OBJNUM( ) or _CUROBJ.
Clauses
<var>
<var> is the memory variable, array element or field specified when the
control was created.
In the following example, three radio buttons with the prompts Apples,
Oranges and Lemons are created. In this example, <var> is a memory
variable named
FRUIT that initializes the radio buttons (since FRUIT equals 2, the
second button is initially selected). The button number is stored to
FRUIT when you choose
a button.
CLEAR
STORE 2 TO fruit
@ 4,2 GET fruit PICTURE '@*R Apples;Oranges;Lemons'
READ CYCLE
<expN1>
expN1> is the number of the button you want to redisplay within a set of
invisible, radio, or push buttons. A button's number is determined by
the order in which
the button prompts are created. In the example above, Apples is created
first and is button number one. The second button created is Oranges;
it is button
number two. The last button, Lemons, is button three.
The following program creates the same buttons as in the previous
example. However, when one of the radio buttons is chosen, the NOORANGE
VALID
routine is executed. The routine disables the Oranges button with SHOW
GET and DISABLE.
CLEAR
STORE 2 TO fruit
@ 4,2 GET fruit PICTURE '@*R Apples;Oranges;Lemons' VALID noorange( )
READ CYCLE
FUNCTION noorange
SHOW GET fruit,2 DISABLE && Disables the second button
_CUROBJ = 1
RETURN .T.
PROMPT <expC>
You can replace the prompt for an individual push button, radio button
or check box with another prompt by including PROMPT <expC>. <expC>
replaces the
original button or check box prompt. You can also change the button or
check box attributes (which determine whether the control is enabled or
disabled, what
hot keys are assigned, and whether it is the default or Esc choice) by
specifying the appropriate special characters with <expC>.
SHOW GET is typically placed in a VALID routine for the check box, push
button or radio button.
In the following example, a check box is created. When the check box is
chosen, the VALID clause routine Newprompt is executed. The routine
changes the
check box prompt and the hot key.
CLEAR
STORE 1 TO check
@ 4,2 GET check FUNCTION '*C \<Checked' SIZE 1,13 VALID NEWPROMPT( )
READ CYCLE
FUNCTION newprompt
IF check = 0
SHOW GET check,1 PROMPT '\<Unchecked'
ELSE
SHOW GET check,1 PROMPT '\<Checked'
ENDIF
RETURN .T.
In FoxPro for Windows and FoxPro for Macintosh, you can use PROMPT to
specify picture files that are displayed on a picture check box, push
button or radio
button when it is enabled, selected and disabled. The PROMPT clause is
ignored if picture files are specified in the PROMPT clause in FoxPro
for MS-DOS.
In FoxPro for Windows, the picture file can be a bitmap file with a .BMP
extension. In FoxPro for Macintosh, you can use a picture file of PICT
type or a .BMP
bitmap file.
Include a set of up to three picture files separated by commas in
<expC>. The first picture file is displayed on the picture check box,
push button or radio button
when it is enabled. The second picture file is displayed when the
picture check box, push button or radio button is selected. The third
picture file is displayed
when the picture check box, push button or radio button is disabled.
ENABLE | DISABLE
Including ENABLE allows the specified control to be selected or chosen.
Including DISABLE prevents the control from being selected or chosen and
displays
the control in disabled colors.
LEVEL <expN2>
You can nest READs by issuing @ ... GET and a READ in a routine called
in an active READ. READs can be nested to five levels.
If you don't include a LEVEL clause, SHOW GET defaults to the current
READ level. Include a LEVEL clause to redisplay a control on a level
other than the
current level. The numeric expression <expN2> can assume the value 1,
2, 3, 4 or 5 corresponding to the READ level of the control to
redisplay. Use
RDLEVEL( ) to return the current READ level.
COLOR SCHEME <expN3> | COLOR <color pair list>
Controls can be redisplayed in the colors you specify. You can specify
a color scheme or a color pair list. For more information about control
colors, see to
@ ... GET and @ ... EDIT - Text Edit Regions.
----------------------------------------------------------------
Rajan Imports has changed - we are now Whispering Smith Ltd. For more
information see our website at www.whisperingsmith.com
Please update your address book with my new email address:
[email protected]
.
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or
disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd
Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700
Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
