Re: Win8 testing

[rik]

On 04/01/2015 11:26 AM, address@hidden wrote:

Subject:

Re: Windows 8

From:

Giorgio De Nunzio <address@hidden>

Date:

04/01/2015 09:31 AM

To:

address@hidden

List-Post:

<mailto:address@hidden>

Content-Transfer-Encoding:

quoted-printable

Precedence:

list

MIME-Version:

1.0

References:

<address@hidden>

In-Reply-To:

<address@hidden>

Message-ID:

<address@hidden>

Content-Type:

text/plain; charset=utf-8; format=flowed

Message:

2

Il 01/04/2015 18:19, John W. Eaton ha scritto:

Has anyone tested the Windows binary distribution of 4.0.0-rc2 on a Windows 8 system?  I remember that there were reports of problems with earlier versions and I'm wondering if those have been fixed. If not, what were/are the problems?

jwe

Hi John,
I have started to test rc2 on w7 and w8.
On w8, apart from the same problems I am having on w7, i.e.:
1) in the GUI, ctrl+C for script interrupting is masked by ctrl+C for copy, so scripts are not interruptible; there is a workaround by shortcut redefinition;
2) pause() does not work as expected (quite severe bug imho),
I am also experiencing a problem concerning figure saving to disk. The problem is not present on all the W8 pcs on which I have tried, only on 2 over 3 of them.
When I plot something, eg a trivial x=1:10;plot(x,x.^2); the plot is ok. When I save the image to a pdf file (which by the way and unfortunately is the only available format), only the axes appear in the created pdf file, no curve. This is really annoying, because at present on those pcs the only way to take a plot and put it somewhere (e.g. a .doc file) is by screen snapshots.
Best regards
Giorgio

Giorgio,

The "Save" or "Save As" command internally calls the saveas/print function.  Just change the filename extension to get a different output.  For example, '.png', 'jpg', etc.

Do the PCs which show only the axes, no curve, have different graphics acceleration hardware from the others?  And does this work

x = 1:10;
plot (x, x.^2, "*-");
set (gca, "color", "none");
print tst.pdf

If it does, then this is an upstream bug in gl2ps which has been fixed but is awaiting the next release to be available to Octave.

--Rik