[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
38.0. "FDV$AFVA and OA$FLD_PUT confuses FMS 'memory'?" by SHALOT::LANPHEAR (Test the water or turn the tide?) Tue Feb 18 1992 18:42
Hi,
I have been working with an unusual customer request to have dynamic
highlighting of fields on a menu form. For example, the menu contains
a number of display only fields, selected from a RMS data-set. If
particular fields meet particular criteria, they should be bold,
reverse, etc. depending upon the condition. I created a menu which
calls some pre-processing (code level) to fill in the fields and then
select the video attributes via the FDV$AFVA routine. This all works
fine, except...
Once I have used FDV$AFVA on a field, FMS thinks that it always has
to repaint that field whenever I touch it again (OA$FLD_PUT), even if I
specify the same value which is currently in the field (including blanks).
It appears that there is some interaction between OA$FLD_PUT and FDV$AFVA
at the FMS level, but it escapes me. If I create a DO script to fill in
the values instead of using the code level DSAB (get fld="value" vs
OA$FLD_PUT), then these same fields are _not_ repainted if they match the
"new" value specified... Any ideas? I see that OAFMS says that FMS
V2.3 was supposed to manage field "memory" so we don't have to, but is
there something else going on with video attributes? (ALL-IN-1 V2.4)
Thanks in advance,
Cheers, Dan'l
T.R | Title | User | Personal Name | Date | Lines
|
---|