On 2009-08-27 09:47+0100 Andrew Ross wrote:
>
> Sorry,
>
> Scrub that. What I was actually doing was pressing return so the second plot
> was with the xwin driver not the xcairo / qtwidget driver. This explains the
> different size windows.
>
> It is interesting that qtwidget followed by xwin cras
Sorry,
Scrub that. What I was actually doing was pressing return so the second plot
was with the xwin driver not the xcairo / qtwidget driver. This explains the
different size windows.
It is interesting that qtwidget followed by xwin crashes. This still looks
like qtwidget is not correctly clean
Alan,
Unfortunately I have the opposite to report. This is Ubuntu jaunty 64-bit
intel. The xcairo driver runs successfully with your test case, although
valgrind shows that it is not clean. Conversely qtwidget seg faults when
trying to open the second page.
With plend replaced by plend1 both dr
Hi Hez:
This is mostly for you but there are some reassuring remarks for Alban here
as well.
On 2009-08-26 15:13-0700 Alan W. Irwin wrote:
> When persistent memory management problems (segfaults, etc.) are identified
> like this, I think it is important to add a simple C test routine to
> demons
On 2009-08-26 13:48-0500 Hezekiah M. Carty wrote:
> While testing the qtwidget and other PLplot qt output devices I ran in
> to two issues. This is on Ubuntu 9.04 64bit, with the system Qt
> version (4.5.0).
>
> The first issue is similar in feel to an long-lived, ongoing Cairo
> problem - callin
