[Lcdproc] Patch for CW1602 USB, lcdproc 0.5.0

[Peter Marschall]

Hi,

On Thursday, 5. October 2006 18:33, Tomislav Secen wrote:
> > Please test and report feedback.
> > The driver should:
> > - be able to show icons as well as horizontal and vertical bars
> > - use the standard heartbeat
>
> Great, this is much better:
> 	-icons are displayed nicely
> 	-bars are OK (at least the few I've seen)
> 	-heartbeat icon flashes nicely in the top right corner.

Thanks for the feedback !
(Especially sicne it is a success report)

> Only issue I encountered was (similar came up before) - when setting some
> menu options, or just entering a certain menu (like
> Options->CwLnx->OnBrightness, lcdvc client menu), the LCD becomes garbled 
> (i.e. displays two blinking hearts, boxes, '%' symbols), sometimes starts
> displaying just '%' symbols over the whole LCD while I'm pressing
> Left/Right keys (is this the screen-saver?), scrolling from right to left.
> Even the "Thank you for using ..." message is garbled (each time in a
> different way) if I kill the daemon after that. Pressing 'X' when the
> garbled characters occur exits the menu and the other (client) screens are
> displayed correctly after that. So only the menus are affected by this
> issue - it seems that this screen-saver mode kicks in in the wrong time,
> and tries to write to LCD faster than it can process chars/commands.

Sorry, your guess with the screen-saver is wrong :-(
LCDproc does not have such a thing.

The menu is built from widgets the same way other screens are,
and the Right key can be mapped to have a special meaning in the menu:
- select the current sub menu (don't know if this was intended ;-)
- move right in input fields

Do you have all the keys mapped in the [server] and [menu] sections
of LCDd.conf ?

Did you try to run the keypad test mode ?
Is the default keyboard mapping as advertized in the LCDd.conf file.

> I can provide the log file if you want ...

I'd rather if you tried to poke around a bit since I have absolutely no idea
what the cause might be.
I doubt it is a problem if the menu code in the server core since the menu
works for various different drivers.
That's why I tend to think of a problem in the driver which is very hard
to debug without the hardware. 
Would you mind to try to hunt the bug ?
(I wrote re-wrote the driver for you - this is what I ask in retur [at least 
the tests above] ;-)

Peter

-- 
Peter Marschall
peter@adpm.de