Search found 482 matches

by dusoft
Sun Mar 17, 2024 12:55 pm
Forum: General
Topic: Gradients (gradient as fill)
Replies: 10
Views: 446

Re: Gradients (gradient as fill)

I might post the library with a bunch of nice polygon handling snippets that uses some recipes from other open source libraries. Or maybe higher level functions centralizing work with 2D bodies (with fixtures and shapes under the roof). I'll see if I have a time provide such library, because I still...
by dusoft
Sun Mar 17, 2024 5:20 am
Forum: General
Topic: Gradients (gradient as fill)
Replies: 10
Views: 446

Re: Gradients (gradient as fill)

Even better examples with full polygon visible.

Gradient starts around the original polygon (boat shaped), but I could make it start around centroid point, this is just matter of setting the scale and drawing...
by dusoft
Fri Mar 15, 2024 7:48 pm
Forum: Libraries and Tools
Topic: Love2D Studio: A free tool to code and test fantastic games on iPad/iPhone
Replies: 36
Views: 195968

Re: Love2D Studio: A free tool to code and test fantastic games on iPad/iPhone

marknote wrote: Fri Mar 15, 2024 12:41 pm As previously stated, I discovered that Lua is a very user-friendly programming language for my son, and love2d is a great framework.
My son's only computer is an iPad, and Love2d Studio makes the pairing perfect :D
Thanks, what a paradigm shift (programming on a tablet/mobile phone), indeed.
by dusoft
Fri Mar 15, 2024 12:09 pm
Forum: General
Topic: Gradients (gradient as fill)
Replies: 10
Views: 446

Re: Gradients (gradient as fill)

You can see it on the screenshot (blue ones, yellow is the original polygon that was used for scaling up). I create couple of scaled up polygons of the same shape just drawing over each other (starting from the outside - from large to small). This efficiently creates a gradient, I can control how ma...
by dusoft
Fri Mar 15, 2024 7:03 am
Forum: Libraries and Tools
Topic: Love2D Studio: A free tool to code and test fantastic games on iPad/iPhone
Replies: 36
Views: 195968

Re: Love2D Studio: A free tool to code and test fantastic games on iPad/iPhone

Hey guys, I am curious about the target users of this app. Can you (if you are willing) provide some info on why do you prefer coding on a mobile phone vs laptop/desktop? Is it because you use mobile phone primarily or you don't have access to a laptop? Is it for doing last-minute changes to a mobil...
by dusoft
Fri Mar 15, 2024 6:54 am
Forum: Support and Development
Topic: Overlapping sensors - Box2D order / behavior
Replies: 8
Views: 536

Re: Overlapping sensors - Box2D order / behavior

Thank you to you both. I have changed my approach now to use non-overlapping trapezoids / polygons (that are touching as seen on the screenshot). This make it easier, but one thing is still tricky. It seems that collision end callback for first sensor is called a second later than collision start fo...
by dusoft
Thu Mar 14, 2024 6:28 pm
Forum: Support and Development
Topic: Overlapping sensors - Box2D order / behavior
Replies: 8
Views: 536

Re: Overlapping sensors - Box2D order / behavior

Indeed, a screenshot should help explaining it. 1 = speed 10 2 = speed 20 3 = speed 30 Arrows show how sensor overlap from the yellow border. Now, when going from outside through 3 to 1, I am getting correct collisions detected (e.g. 30,20,10). However, when starting in 1, I get all three collisions...
by dusoft
Thu Mar 14, 2024 3:20 pm
Forum: Support and Development
Topic: Overlapping sensors - Box2D order / behavior
Replies: 8
Views: 536

Re: Overlapping sensors - Box2D order / behavior

OK, so now I have created touching sensors (e.g. not overlapping, but having one pixel (one line) in common) and I am getting the same results. I will have to experiment with pre/post-solve callbacks. I'll be glad to accept any suggestions regarding this.
by dusoft
Thu Mar 14, 2024 11:30 am
Forum: Support and Development
Topic: Overlapping sensors - Box2D order / behavior
Replies: 8
Views: 536

Overlapping sensors - Box2D order / behavior

I have two overlapping sensors using love.physics module. Let's call them speed 10 and speed 20. It seems that Box2D model will not properly test for collisions when sensors are overlapping. E.g. body going from speed 10 to speed 20 (while speed 20 overlaps speed 10 sensor) will not report collision...