On Tue, 2005-11-29 at 17:15 +0100, Denis Oliver Kropp wrote:
> Quoting Nathanael D. Noblet:
> > Hello,
> > Is it possible from a DirectFB app to disable/enable an input
> > module? I have a touch screen (gunze) that needs to be calibrated, but
> > part of the problem is that the input module written for it is loaded. I
> > tried --dfb:disable-gunze but it isn't disabled when running (I still
> > get output from the module loading).
>
> Between DirectFBInit() and DirectFBCreate() you can call:
>
> DirectFBSetOption( "disable-module", "gunze" );
Okay, so that is fine for the standalone DirectFB calibration program.
However for the kiosk I'm building, going into and out of the
calibration through the program would be nice. I tested it by modifying
the standalone program. After the calibration, and before I print out
the calibration data, I do this
DrawRects("Done");
ReleaseFonts();
if(mouse != NULL)
mouse->Release(mouse);
buffer->Release(buffer);
primary->Release(primary);
dfb->Release(dfb);
DirectFBSetOption( "enable-module", "gunze" );
DFBCHECK (DirectFBCreate (&dfb));
and go on to re-initialize everything drawing to the screen. It works
in that it doesn't crash or anything. The screen flickers between the
release/create
surface calls. Which I'm okay with. However looking at the resultant output, it
doesn't seem that DirectFBSetOption("enable-module","gunze"); worked. Is it
supposed to? Is what I'm wanting to do possible?
--
Nathanael D. Noblet
Gnat Solutions
http://www.gnat.ca/
T 250.385.4613
C 250.893.4613
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
