bugGNU Octave - Bugs: bug #53214, area.m needs update to implement...


bug #53214: area.m needs update to implement ShowBaseline and other properties

Submitted by:  Marshall <marsian>
Submitted on:  Sat 24 Feb 2018 01:44:54 AM UTC  
Category:  Plotting Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Matlab Compatibility
Status:  Confirmed Assigned to:  None
Originator Name:  Marsian Open/Closed:  Open
Release:  dev Operating System:  Any

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Wed 28 Feb 2018 01:14:14 AM UTC, comment #6:

Yes, Matlab sets x limits at [1,10]. See the attached figure. It also happens with plot...

(file #43410)

Marshall <marsian>
Tue 27 Feb 2018 10:04:22 PM UTC, comment #5:

Since you have access to Matlab, what does

look like? Octave sets the x limits at [0, 10] which seems silly. It looks like it would be better to set the limits at [1, 10] and closely hug the data.

Rik <rik5>
Project Administrator
Tue 27 Feb 2018 09:56:52 PM UTC, comment #4:

This works great for me!

Marshall <marsian>
Mon 26 Feb 2018 05:48:02 PM UTC, comment #3:

The area.m function has not been updated now that patch implements facealpha. In fact, there are several unimplemented properties.

I see that BaseLine and ShowBaseline are unimplemented, although BaseValue is. Also, XDataSource, YDataSource, and XDataMode are likewise not implemented.

This was a pretty easy fix so I added support for EdgeAlpha and FaceAlpha in this cset (http://hg.savannah.gnu.org/hgweb/octave/rev/1cacfebaed3e).

Rik <rik5>
Project Administrator
Mon 26 Feb 2018 03:30:12 PM UTC, comment #2:


>> area(rand(10),'facealpha',0.5)

hold on
hold off
error: set: unknown hggroup property facealpha
error: called from
area>__area__ at line 188 column 7
area at line 117 column 10

It fails on the first call above. If working properly, it would continue to the second area call and would appear with some transparency. I know transparency has been implemented with some of the other functions now in dev (patch, surface, ...), so allowing transparency for area would be ideal. If transparency can't be added, at the very least it shouldn't error out.

Marshall <marsian>
Sun 25 Feb 2018 05:32:41 PM UTC, comment #1:

Which commands are you running to produce the error? Which error are you seeing exactly?

I won't be able to look into this during the next two weeks or so. But might have a look at this later if no one else wants to check earlier.

Markus M├╝tzel <mmuetzel>
Project Member
Sat 24 Feb 2018 01:44:54 AM UTC, original submission:

Use of the 'area' function with the facealpha property causes an error. At the very least the option shouldn't cause an error for matlab compatibility, but even better would be to implement it.

I'm using a dev version on Win 10 compiled on Feb 1st, and I don't think any changes since then would have fixed this.

Marshall <marsian>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files
file #43410:  area10.PNG added by marsian (23KiB - image/png)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by marsian (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.




    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-02-28 marsian Attached File- => Added area10.PNG, #43410
    2018-02-26 rik5 StatusNeed Info => Confirmed
        Summaryfacealpha property causes error when used with area() => area.m needs update to implement ShowBaseline and other properties
    2018-02-25 mmuetzel StatusNone => Need Info

    Back to the top

    Powered by Savane 3.3