Quoting Vincenzo Ampolo:
> IDirectFBEventBuffer::WaitForEventWithTimeout(unsigned int, unsigned
> int) -> Operation timed out!
> (!) [10318: 0.000] --> Caught signal 6 (unknown origin) <--
This signal is caused by an uncaught exception. You should add at least
one exception handler around your DirectFB code. Something like:
int
main( int argc, char *argv[] )
{
Simple app;
try {
/* Initialize DirectFB command line parsing. */
DirectFB::Init( &argc, &argv );
/* Parse remaining arguments and run. */
if (app.Init( argc, argv ))
app.Run();
}
catch (DFBException *ex) {
/*
* Exception has been caught, destructor of 'app' will deinitialize
* anything at return time (below) that got initialized until now.
*/
std::cerr << std::endl;
std::cerr << "Caught exception!" << std::endl;
std::cerr << " -- " << ex << std::endl;
}
return 0;
}
Anyways, the method shouldn't throw an exception due to a timeout,
because it's an essential part of its semantic.
What should I do? Add a bool return value like in HasEvent()?
But what would true mean then? Event or timeout? Or return DFBResult
with DFB_OK or DFB_TIMEDOUT?
--
Best regards,
Denis Oliver Kropp
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
