octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44916] Printing Qt-drawn figures produces fau


From: Martin Kunz
Subject: [Octave-bug-tracker] [bug #44916] Printing Qt-drawn figures produces faulty files
Date: Tue, 05 May 2015 15:37:08 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

Follow-up Comment #25, bug #44916 (project octave):

Response to Dan (comment #24)

I did not change settings after installation, so both machines produce plots
with default settings. The axes equivalent to figure position is axis
position, right?

I ran the test script again on both machines and checked the properties of
figure 2:


>> get (2,"position")
ans =
   300   200   560   420
>> get (0,"defaultfigureposition")
ans =
   300   200   560   420
>> get (get (2,"children") , "position")
ans =
   0.13000   0.11000   0.77500   0.81500
>> get (0,"defaultaxesposition")
ans =
   0.13000   0.11000   0.77500   0.81500


The results are exactly the same on both systems.

The second test you proposed was not so easy to perform because, as I wrote
before, the result is not deterministic: Sometimes the curve is fine,
sometimes broken, sometimes it has wild lines. Same for the axes, it needed
several runs until I got an EPS with green background and a missing axis. The
file f2greenBG.eps was created on the "problematic" machine 1 with the
following commands:


figure();
fflush(stdout);
x = 1:1000;
y = sin (x/300);
plot (x,y);
set(gca, 'color', [0 1 0]) 
xlabel ("Time in s")
ylabel ("\Omega")
fprintf ("nSaving figure 2n");
print -dpng -r0 f2.png
print -dpdf -r0 f2.pdf
print -dsvg -r0 f2.svg
print -depsc -r0 f2.eps


After creation, I renamed the file from f2.eps to f2greenBG.eps in order to
prevent it from being overwritten.

To me it seems pretty clear that the x-axis is really missing, not covered -
the lower background triangle is missing and opening the EPS with Inkscape I
cannot find a line for the axis.

Doesn't the randomness of the error indicate that Rik is probably right and we
are facing something thread-related here, a race condition maybe? One big
difference between my two systems is that the machine that produces faulty
files is much faster than the other (3.3GHz with graphics card vs. 2.4GHz with
onboard graphics).

(file #33925)
    _______________________________________________________

Additional Item Attachment:

File name: f2greenBG.eps                  Size:98 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44916>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]