[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: things for 3.0
From: |
Shai Ayal |
Subject: |
Re: things for 3.0 |
Date: |
Fri, 12 Oct 2007 15:25:22 +0200 |
On 10/12/07, David Bateman <address@hidden> wrote:
> Shai Ayal wrote:
> > On 10/12/07, David Bateman <address@hidden> wrote:
> >
> >> John W. Eaton wrote:
> >>
> >>> I'd like to do the following for 3.0.
> >>>
> >>> * Update various README files.
> >>>
> >>> * Update NEWS file. There is no way we are going to try to mention
> >>> all the changes since 2.0.17 or even 2.1.73, but we should mention
> >>> important user-visible changes that could cause backward
> >>> compatibility problems. Are there additional items that we should
> >>> mention?
> >>>
> >>> * Update the refcard.
> >>>
> >>> * Update installation instructions.
> >>>
> >>> * Remove obsolete files (for example, is FLEX.patch still needed?)
> >>>
> >>> * Any other similar items?
> >>>
> >>> As none of these items involve code in Octave itself, I think they
> >>> should be safe to do between 2.9.15 and 3.0 with little testing.
> >>>
> >>> Comments?
> >>>
> >>> jwe
> >>>
> >>>
> >>>
> >>>
> >>>
> >> There is one handle graphics bug that should be addressed before 3.0.
> >> That is the multiple patch problem.. My test case for this issue is
> >> something like
> >>
> >> t1 = (1/16:1/8:1)'*2*pi;
> >> t2 = ((1/16:1/8:1)' + 1/32)*2*pi;
> >> x1 = sin(t1);
> >> y1 = cos(t1);
> >> x2 = sin(t2);
> >> y2 = cos(t2);
> >> h = patch([x1,x2],[y1,y2],cat (3,[0,0],[1,0],[0,1]));
> >> pause(1);
> >> set(h,'FaceColor','r');
> >>
> >> showing two patches drawn that are blue and green that can then both be
> >> changed to red using the handle.. I don't think this needs fixing for
> >> 2.9.15, but for 3.0 it definitely should be fixed.
> >>
> >
> > I attach a patch for __patch__.m which fixes this bug.
> >
> > 2007-10-12 Shai Ayal <address@hidden>
> >
> > * plot/__patch__.m: will now return handles of all patch objects
> > created
> >
> >
>
> No this isn't the solution... This is the behavior of the fill and fill3
> functions. The patch function returns a single handle to all of the
> patches.. I have a partially working patch to this issue and will try to
> sent it soon..
So if I understand correctly, what the current patch.m does in your
test case is create two patch objects , and you wish for it to make
one patch object?
> D.
>
>
> --
> David Bateman address@hidden
> Motorola Labs - Paris +33 1 69 35 48 04 (Ph)
> Parc Les Algorithmes, Commune de St Aubin +33 6 72 01 06 33 (Mob)
> 91193 Gif-Sur-Yvette FRANCE +33 1 69 35 77 01 (Fax)
>
> The information contained in this communication has been classified as:
>
> [x] General Business Information
> [ ] Motorola Internal Use Only
> [ ] Motorola Confidential Proprietary
>
>
- things for 3.0, John W. Eaton, 2007/10/12
- Re: things for 3.0, David Bateman, 2007/10/12
- Re: things for 3.0, Shai Ayal, 2007/10/12
- Re: things for 3.0, David Bateman, 2007/10/12
- Re: things for 3.0,
Shai Ayal <=
- Re: things for 3.0, David Bateman, 2007/10/12
- Re: things for 3.0, Shai Ayal, 2007/10/12
- Re: things for 3.0, David Bateman, 2007/10/12
- Re: things for 3.0, Shai Ayal, 2007/10/12
- Re: things for 3.0, David Bateman, 2007/10/12
- Re: things for 3.0, David Bateman, 2007/10/12
- Re: things for 3.0, David Bateman, 2007/10/12
- Re: things for 3.0, John W. Eaton, 2007/10/12
- Re: things for 3.0, David Bateman, 2007/10/13
- Re: things for 3.0, John W. Eaton, 2007/10/13