fillPath doesn't fill path

true though! i guess it’s just a steep learning curve. but i guess that’s fine. if we didn’t struggle sometimes we wouldn’t ever come up with weird and desperate alternate solutions xD

(did this shortly before i finally figured out the path-problem)

1 Like

OT: beautiful moiree effect :slight_smile:
Great to showcase sampling artifacts

1 Like

lol so false. your own example code is doing exactly that!

Did you look at the documentation for the Path class before you started using it?
There is a very clear usage example that shows you everything you need to know about how to create and display Path instances.

https://docs.juce.com/master/classPath.html#details

Also, there is a ton of usage of the Path class in Projucer and the Demo projects. You can just search the source code of those projects for Path being used.

Come on, I think it’s ok now…

1 Like

you’re right that the link you provided shows how to make a path that correctly knows it can be filled. but there is no word about the fact that using line segments kinda destroys this functionality, so i’d personally suggest the juce devs to add some words about it or make that clear in a demo project

https://docs.juce.com/master/classPath.html#a88f8efbb76ff2f281aa528e3ad2b63a7

Adds a line with a specified thickness.

The line is added as a new closed sub-path. (Any currently open paths will be left open).

It’s all there in the documentation. If you’re going to take anything away from this thread, let it be learning to read the documentation :slight_smile:

1 Like