[rkward-cvs] rkward/rkward/rbackend rinterface.cpp,1.39,1.40

Thomas Friedrichsmeier tfry at users.sourceforge.net
Thu Nov 3 21:35:52 UTC 2005


Update of /cvsroot/rkward/rkward/rkward/rbackend
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27848/rbackend

Modified Files:
	rinterface.cpp 
Log Message:
small stuff

Index: rinterface.cpp
===================================================================
RCS file: /cvsroot/rkward/rkward/rkward/rbackend/rinterface.cpp,v
retrieving revision 1.39
retrieving revision 1.40
diff -C2 -d -r1.39 -r1.40
*** rinterface.cpp	3 Nov 2005 19:34:29 -0000	1.39
--- rinterface.cpp	3 Nov 2005 21:35:50 -0000	1.40
***************
*** 128,134 ****
  	if (e->type () == RCOMMAND_OUTPUT_EVENT) {
  		RThread::ROutputContainer *container = (static_cast <RThread::ROutputContainer *> (e->data ()));
! 		// we've already made sure, there is an existing receiver in RThread
  		container->command->receiver->newOutput (container->command, container->output);
  		delete container;
  	} else if (e->type () == RCOMMAND_IN_EVENT) {
  		watch->addInput (static_cast <RCommand *> (e->data ()));
--- 128,140 ----
  	if (e->type () == RCOMMAND_OUTPUT_EVENT) {
  		RThread::ROutputContainer *container = (static_cast <RThread::ROutputContainer *> (e->data ()));
! 	// we've already made sure, there is an existing receiver in RThread
  		container->command->receiver->newOutput (container->command, container->output);
  		delete container;
+ /* TODO: not quite good, yet, but something like this should be done:
+ 	// output events can easily stack up in the hundreds, not allowing GUI events to get through. Let's block further output events for a minute (using MUTEX_LOCK) and then catch up with the event queue
+ 		MUTEX_LOCK;
+ 		qApp->processEvents ();
+ 		MUTEX_UNLOCK;
+ */
  	} else if (e->type () == RCOMMAND_IN_EVENT) {
  		watch->addInput (static_cast <RCommand *> (e->data ()));





More information about the rkward-tracker mailing list