On Sep 11, 2013, at 4:16 AM, Vlad Bogolin wrote: > I modified the code so that every time Tcl_DoOneEvent is called > QApplication::processEvents is also called so that there aren't any > modification to the code that have to be done besides checking for Tk events > non-blocking. I couldn't figure out a method to avoid this since being > blocked and waiting for Tk events stops from processing Qt ones. I haven't > modified the code in bwish (the call to qt_tk_processEvents that now only > processes Tk ones non-blocking because DM_QT is not defined in bwish and I > want to process events non-blocking just when qt dm is enabled. Should I > leave it like this (and change the name to be more appropriate) or should I > process all events non-blocking?).
I still think another solution is needed. Bwish is going to go away. Putting code into bwish will make it even harder for it to go away without breaking your new Qt interface. What about adding it to src/libtclcad/tclcad.c:Tclcad_Init() instead? That should get run when "package require Tclcad" is run, which will be before nearly everything. Cheers! Sean ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
