Fixed a bug that hindered horizontal layout.

Please, post screenshots. AFAIK LOVE uses bitmaps internally for font rendering. Even if you provide TTF, an internal bitmap font will be created from it. This could be the cause.

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...

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...

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

Thanks, what a paradigm shift (programming on a tablet/mobile phone), indeed.

Thanks for your insight!

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...

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...

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...

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...