[lcdproc] Multiple inputs and outputs and clients OH MY!

[Joris Robijn]

> Right, but then you tell the *driver* which size it has rather than the
> LCDd. Display size should really be a driver option. Same for emulated
> cellwidth.

Big AGREE

> > Also, since clients can send custom graphic characters, they need to
> > know what size the cells are.

This should be driver dependant, and therefor dependant on the part of 
the framebuffer that we are currently writing on. So this introduces a 
problem: defining characters and multiple displays do not go together.

> Exactly. Imagine my setup here:
> 3 Displays with 3 different drivers:
> A: SED1520, size 20x4, cellwidth 6, 256 custom chars
> B: STV5730, size 28x11, cellwidth 4, 0 custom chars
> C: HD44780, size 16x4, cellwidth 5, 8 custom chars

OK, question: Do you really (now be honoust) really want to couple 
these displays to become one large display ?  Or do you use the 
displays all for different functions/programs, so they could better use 
a separated server ?

Joris

-- 
 Joris Robijn <joris@robijn.net>
 Home: 053 4311 553
 Mobile: 06 288 41 964

 // To understand recursion, we must first understand recursion


-----------------------------------------------------------
To unsubscribe from this list send a blank message to
lcdproc-unsubscribe@lists.omnipotent.net