[Lcdproc] Highlighting pictograms
bsdfan at nurfuerspam.de
Tue Nov 8 19:43:29 UTC 2011
On 05.11.2011 14:17, Anders wrote:
> On 11/03/11 02:38, Stefan Herdler wrote:
>> And if anyone has a better idea how to indicate highlighting let it us know.
> Instead of a single int for each icon, use an array, or a set of
> properties. That way each icon can have any number of attributes. I
> could easily see (On/off, Strength, highlighted) etc. Futhermore, what
> if an icon is e.g. a square where you can on/off each of the top,
> bottom, left, right sides individually? If the interface was an array,
> that functionality could easily be exposed to the application.
> It seem a bit short sighted to fold everything iconish into a one
> dimensional abstraction. Why don't we allow the applications to query
> the caps of the icons and act on those caps? The list of caps could
> expand as needed over time, and the same query, get, set protocol could
> be used forever.
that makes sound. And there are things like the spinning disc icon of
the imonlcd driver on which we have not talked in detail yet.
We probably need some more advanced data structure in LCDd core.
However, at the very end the task of the driver is to switch some light
on or off. If we want to support e.g. RGB colored things, a simple int
will not be sufficient, but for now I think it's fine.
If we treat "highlighting" as a completely different thing than "the
value", we may need to define this as an extra property. Then even
numeric type pictograms can be highlighted.
If we treat it as "more intense than just on" for boolean type
pictograms these become "tri-state" pictograms and I would assign them
"0" = off, "1" = on, and "2" = highlighted. For driver not supporting
highlighted pictograms than "on" is anything else than zero or anything
Anyway I'd like to avoid the "-1" on the interface as "-1" is used as
UNSET_INT in other areas of the code.
More information about the LCDproc