Re: Using SFLCHCCTL in DDS

["M. Lazarus" <mlazarus@xxxxxxxx>]

Booth,

At 12/29/02 01:55 AM, you wrote:
> Wow, this is neat.  Now we can select & unselect one item, or many items,
> all with mouse clicks, and all done easily.
 It *is* pretty neat.  Unfortunately, I think that it's a case of "too
little, too late", since they could have integrated this into a real GUI,
but that's for a bygone holy war...


> 1) I tried your code and things seemed to work nicely here.  Your subfile
> starts on line 6.  Is it possible that something in lines 1 thru 5 are
> causing troubles?  I saw no turquoise at all.
 They use Rumba here (at least for now).  Maybe that's the cause of the
weird colors combo.


> 2) I didn't try changing colors beyond the defaults provided for the various
> values in the SFLCHCCTL field.  I did notice the following in the manual:
> The CHCAVAIL, CHCSLT, and CHCUNAVAIL keywords can be used to indicate the
> color of the items within the selection list, when the list is displayed on
> a color display station. The CHCAVAIL keyword indicates the color of the
> items within the list which are available for selection. The CHCSLT keyword
> indicates the color of the selected items. The CHCUNAVAIL keyword indicates
> the items on the list which are not available for selection. These keywords
> can be used in a subfile control record only if SFLSNGCHC or SFLMLTCHC
> keywords are also used."
 I'll have to play w/ the CHCAVAIL and CHCSLT keywords to see if I can
make it do what I want.


> 3) because of the way that the field changes color when its selected, I'd
> suspect adding more than one visible field to a subfile might be confusing.
>  As easy as it is to concatenate fields with EVAL now though, is this
> really a problem?
 Not at all.  I just found it surprising.  It does mean though that if I
want to add some attribute to the field I would have to do it manually via
hex attributes, which is less than desirable, IMHO.

 -mark