On 2009-03-13 14:20-0000 Andrew Ross wrote: > On Fri, Mar 13, 2009 at 01:58:18PM +0000, Alban Rochel wrote: >> Andrew Ross wrote: >>> It does however fix things for me and ctest again runs successfully. >>> >>> Andrew >>> >> >> I'm glad you managed to fix this. Thanks a lot! >> >> Alban > > No problem. You may want to test use of multiple devices (example 14 is > good for this). A couple of problems emerge. > > 1) If you run example 14 with -dev qtwidget then you can't finish the > application. Closing both windows still leaves the example running. This > doesn't happen with single window examples. > > 2) If you run example 14 with qtwidget on 1st stream and qt file device on > second stream then everything runs ok. If you try the Qt file device > first then qtwidget you get a segmentation fault since the application > has not been initialised as a GUI app. This is as I predicted. > > I think the long-term solution to 2) is to work out what else has to be > done for a GUI app to ensure it is properly initialised. In that case > we can always make the QApplication instance a GUI enabled app and all > devices will work.
Hi Alban: Earlier today (revision 9765) I applied your patch that introduces a mutex with the goal of making the qt device driver thread safe. With this change issue (1) seems to be addressed, and no new issues were introduced for the qt device which is why I applied your patch. However, the paging and GUI closing behaviour is not correct for qtwidget since the slave pages independently of the master and also can be closed independently of the master. Run ./x14c -dev xwin in the installed examples/c directory to see the correct paging and GUI closing behaviour. When the master page is changed, so is the slave page. When the master page is closed (by hitting enter, see below) so is the slave GUI closed. When an attempt is made to change the page of the slave or close it (by hitting enter), nothing happens. Note, -dev xwin uses the enter key to move forward in pages and after the last page close the GUI, and that feature would be nice to have for qtwidget as well. However, that wish-list item is independent of the master/slave paging behaviour and GUI closing behaviour issue. I also found that your patch does not fix issue 2. I confirm that if you run ./x14c -fam and specify first qtwidget and second epsqt, all is well, but if epsqt is specified first, and qtwidget second, you get a segfault. If you specify psc first and xwin second all is well and similarly for xwin first and psc second. Please let us know if you have trouble confirming the above issues. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
