In the fisica library what makes setFill, setStroke and setStrokeWeight methods different?

monkstone

In the fisica library what makes setFill, setStroke and setStrokeWeight methods different?

in Contributed Library Questions • 6 months ago

Recently I've had some success in converting some of the fisica library examples to run using ruby-processing, however there is some odd behaviour that I do not understand.

When I try to run the sketches using the built in jruby-complete, the following methods are not detected:- setFill, setStroke and setStrokeWeight of FPoly and FBlob classes, if I comment out the offending lines the Bubbles sketch for example run as expected (so why are these methods different?)

If I use an external JRuby these methods are detected and the sketches run as expected.

Replies(4)

GoToLoop

Re: In the fisica library what makes setFill, setStroke and setStrokeWeight methods different?

6 months ago

I've found these perusing its current source code within FBlob.java.

The actual implementation (or part of it) seems to be within FDrawable.java.

Sometimes going up to Fisica.java:

public void setFillColor(int col) {
super.setFillColor(col);
if (m_joint != null) {
m_joint.updateStyle(this);
}
}
public void setStrokeColor(int col) {
super.setStrokeColor(col);
if (m_joint != null) {
m_joint.updateStyle(this);
}
}
public void setStrokeWeight(float col) {
super.setStrokeWeight(col);
if (m_joint != null) {
m_joint.updateStyle(this);
}
}

monkstone

Re: Re: In the fisica library what makes setFill, setStroke and setStrokeWeight methods different?

6 months ago

Yeah I realised the methods were inherited, I wonder if the depth of inheritance might have something to do with it, since generally jruby makes a pretty good job of coping with inherited methods.

Since jruby-complete was only really included in ruby-processing to support export (as either Applet or Application), I investigated dropping it, in favour of using an installed jruby, but when I did that I ran in to other problems the processing shader (and planets sketch amongst others) examples won't run (this time I get Java::Lang::NullPointerException), this time the sketches work fine using jruby-complete

so I'm reluctant to do that, (plus supplying jruby-complete with ruby-processing is a means of ensuring a degree of version control).

monkstone

Re: In the fisica library what makes setFill, setStroke and setStrokeWeight methods different?

6 months ago

I think I might have the answer and is not pretty, the intermediate class (FDrawable) is abstract, but worse still is not declared public, I think this is the likely cause of the problem.

GoToLoop

Re: In the fisica library what makes setFill, setStroke and setStrokeWeight methods different?

6 months ago

Indeed it seems like every class from package fisica has public access, but FDrawable!

It means only classes from that package can access it!

Perhaps he may have forgotten it?! Better ask him to put public in there too!

Top Reply