[lcdproc] LCDproc .4-pre9 + Matrix Orbital

[Harald Klein]

"Eric Z. Ayers" wrote:
> 
> Harald Klein writes:
> ...
>  > > Seriously, I still see some filckering, this time in the upper left
>  > > two 'blocks' on the screen.  This occurs on the server screen as well
>  > > as my client screen.  Is anyone else seeing this?
>  >
>  > i have a lcd and no problems.
>  >
>  > >
>  > > ----------------------------------------------------------------------------
>  > >
>  > > On another note:  I'm interested in a menu system that launches
>  > > scripts (and allows the user to enter certain data)  The notes say
>  > > this is unimplemented.  Has there been any interest in continuing the
>  > > implementation of menus in the server? I've got programmers available
>  > > to work on it if you're interested in patches to make this work.
>  >
>  > There is a redisign in progress for the 0.5 version.
>  > I think the menu would be a great idea, not only for clients which can
>  > offer configuration menus, but also for a menu given via the config file to
>  > start clients, start programs/scripts, kill them, ...
>  >
>  > It would be great if you could offer some resources to the project.
> 
> OK, I see flickering in my terminal window if I run the 'curses'
> driver, which makes me think that the way the server does refreshes is
> causing the problem with this type of LCD.
> 
> Another theory I have is that this power supply is only 4.5 volts and
> is throwing the whole thing off... (but nevermind that... back to the
> first theory!)

maybe.. check with a voltmeter

> 
> My guess is that some of the other types of LCD require that you
> constantly refresh the screen or else the image will just fade away.
> Can anyone confirm this?

No, i think the update is 8 times/second because some stats are nice to
see instantly updated (cpu bar ...)
I don't have a hdxxx display but i dont think it needs constant refresh.


> 
> To eliminate flicker for 'smart' devices that handle refresh, I
> believe that LCDproc would have to sort of 'double buffering' of the
> screen. What I mean is that the server maintains an image of what the
> current screen looks like, then builds what the next screen will look
> like in memory, and instead of issuing a 'clear' command between
> paints, it would just issue a 'home' command and repaint only the
> characters that are different between the next and current look like
> (if any characters had changed at all!)
> 
> It looks like this might not be TERRIBLY difficult to implement...

yep.

Hari

> 
> -Eric.

-- 
- Never trust a man who can count to 1,023 on his fingers

pub  1024D/A877CBC6 1999-12-28 Harald Klein _linux@chello.at_
sub  4096g/1577CF5F fp = EE17 F2F0 7986 FDC6 F147  B826 3FA1 452A A877
CBC6


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