On Wed, 2005-06-01 00:07:38 +0200, Henk <[email protected]> wrote: > I know this 7-segments stuff probably won't be used widespread much but it > could be important to have similar projects use the same notation, and > use the same concepts. I don't know if a real API is really needed for that. For example, I played a bit with the (single) 7-segment display of one of my VAXen running Linux. Other VAXen only have 8 LEDs in a row. Using these LEDs for debugging, I most probably just want to output *anything* to the LEDs so I just use defined constants for that. However, the principle could be reversed by using a 7-segment "font", a mapping function and an initializer which specifies which bit belongs to which bar of the 7-segment display... But maybe it's really worth mplementing it as a library function... MfG, JBG -- Jan-Benedict Glaw [email protected] . +49-172-7608481 _ O _ "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
Attachment:
signature.asc
Description: Digital signature
- References:
- Prev by Date: Re: TASK_NONINTERACTIVE (was: Machine Freezes while Running Crossover Office)
- Next by Date: Re: [patch] TASK_NONINTERACTIVE (was: Machine Freezes while Running Crossover Office)
- Previous by thread: [RFC] new 7-segments char translation API
- Next by thread: Re: [RFC] new 7-segments char translation API
- Index(es):
 |