Re: Separate icon area: interface for drivers?

Hello everybody!


Since writing the MD8800 driver I am thinking about a "clean" and 
universal useable solution.
(I guess I was the one who started to (mis)use the output function to 
control the icons. O:-) )
I'll tell you, my preferred solution would look like:


There so many different displays out there, why don't we let the drivers 
define the names of Icons?
For the common icons we may suggest some recommend icon-names like HDD0, 
HDD1, CD0...
This open system makes it easy to add new Icons and it is expandable for 
new currently unknown features.

The client should be able to get the list of the Icons the Display.
The List could look somehow like this: "iconname,icontype HDD1,icon 
Volume,bar Antenna,bar Mail,icon ...."
According to the "icontype" the client knows what functionality each 
Icon provides and could choose which one to use.


The server only needs to provide a view generally useable Prototypes.
Let me explain in a few words what i'm thinking about:

The basic type could be a simple integer type.
This type of icon (/ special-function) accepts an 32 bit "int"eger value.
There is no further definition what happens when set.
This is made intentionally, so the programmer of the Driver is free to 
use this type for his own purposes.
For example it could be used to tune some exotic functions of the display.

The "icon" type accepts one 32 bit integer too. It's basically identical 
to integer type with some additional definitions.
A value of "0" means "off"
A value grater 0 means icons is light
At value below 0 the icons is light and highlighted.
Depending on the Display this could mean a red frame around, a kind of 
animation or just a blinking Icon.
Maybe we should also accept keywords like "on" "off" and "highlight".

"Bar"graphs could be controlled similar.
We only need to define the value of the full Bar.
I suggest 100 or 1000 so the clients could calculate in percent or promille.
Again a value below 0 activate a kind of highlighting.
At a antenna like bar this could be "scanning animation" for example.

We could also define a Spectrumanalyzer, which is just a group of bars.


I would treat the "play" "record" "stop" ... Icons as separate Icons.
I don't wart to limit the client in setting these Icons.
On a HTPC system it is not unusual to activate the "record" and "play" 
Icon at the same time.
Playing some media with a recording-process in the background would 
result in that condition.


Btw:
I own a Futaba MDM166 and I may help adapting this driver.

Regards
Stefan