[Lcdproc] New LCDproc driver
NeZetiC
nezetic@gmail.com
Sun Aug 20 18:08:02 2006
Hello,
> All patches committed to CVS with a slight modification in
> clients/lcdproc/mode.c to avoid having init_flag hanging around.
>
> Please try.
Configure and compilation without any error, but there is some =20
problems :
- The eyeboxone.docbook file is missing in "docs/lcdproc-user/=20
drivers/" path...
But this file is in docs.patch file and this patch works and create =20
this file when I use it.
- Your modification in mode.c break my patch, and if you compile =20
lcdproc using the CPPFLAGS=3D-DLCDPROC_EYEBOXONE, lcdproc report errors.
If you read my patch again : eyebox_screen(m->which,0); must be call =20
AFTER a new screen is created by lcdproc (and so after status =3D m-=20
>func(m->timer, display, &(m->flags));).
So I need to save the "m->flags& INITIALIZED" state before "m->func" =20
call, in order to execute my init function after if it's the first call.
{
static int status =3D -1;
int old_status =3D status;
int init_flag =3D -1;
if (m && m->func) {
init_flag =3D (m->flags & INITIALIZED);
status =3D m->func(m->timer, display, &(m->flags));
#ifdef LCDPROC_EYEBOXONE
/* Eyebox Init */
if(init_flag =3D=3D 0)
eyebox_screen(m->which,0);
/* Eyebox Flush */
eyebox_screen(m->which,1);
#endif
}
With your modification, eyebox widgets aren't added to new screens, =20
and the server say something like that :
Unknown widget id (eyebo_cpu)
widget_set
C
eyebo_cpu
1
2
/xB20
Best regards
C=E9dric