octave-maintainers
[Top][All Lists]
Advanced

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

Re: Octave-maintainers Digest, Vol 112, Issue 43


From: Rik
Subject: Re: Octave-maintainers Digest, Vol 112, Issue 43
Date: Mon, 20 Jul 2015 22:23:12 -0700

On 07/20/2015 10:14 PM, address@hidden wrote:
Subject:
Re: Problem with patch () under Octave 4.0.0
From:
Julien Bect <address@hidden>
Date:
07/20/2015 10:14 PM
To:
address@hidden
CC:
address@hidden
List-Post:
<mailto:address@hidden>
Precedence:
list
MIME-Version:
1.0
References:
<address@hidden> <address@hidden>
In-Reply-To:
<address@hidden>
Message-ID:
<address@hidden>
Content-Type:
multipart/alternative; boundary="------------010506060208080904020207"
Message:
3

Le 21/07/2015 05:54, Rik a écrit :
On 07/20/2015 08:37 AM, address@hidden wrote:
Subject:
Problem with patch () under Octave 4.0.0
From:
Julien Bect <address@hidden>
Date:
07/20/2015 08:37 AM
To:
Octave Maintainers <address@hidden>
CC:
address@hidden
List-Post:
<mailto:address@hidden>
Precedence:
list
MIME-Version:
1.0
Message-ID:
<address@hidden>
Content-Type:
multipart/mixed; boundary="------------080208050708070802080501"
Message:
1

Hello all,

A colleague just showed me a problem that he is facing with the patch () function in Octave 4.0.0.

A script that examplifies the problem is attached, with graphical output from Octave 3.8.2 + FLTK (the expected result) and Octave 4.0.0 + qt and FTLK (no more color on the rectangles).

I have checked with Matlab 2012b and the script works there as it was working in Octave 3.8.2.

This looks very much like a regression to me, but perhaps am I missing something ?

Has anyone met this problem before ? Is it a known regression or should I file a bug report ?

Julien,

I can confirm this is a regression.  Please file a bug report along with the example script and files.

--Rik

Done : https://savannah.gnu.org/bugs/index.php?45593.

Any idea where this might come from ?

Very likely libinterp/corefcn/gl-render.cc in the routine draw_patch().  It's pretty complicated, and I did a lot of work to get it to be Matlab compatible for all sorts of different input combinations.  Apparently there is a corner case I missed.

--Rik

reply via email to

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