Build 293.10 - Release version

Problem Resolve.
Thanks Fernando.

This probably isn't worth your while, since there probably aren't many people other than me who would particularly want this. But is there any chance you could add a List View mode to the Layers toolbar (ie. no thumbnail - just layer names and numbers)? It would save some horizontal real estate (allowing us to reduce the width by ~100px while still seeing full layer names). It would also allow those of us who use dozens of layers to see them all at once.

Quote:

---

Originally Posted by Volnaiskra

This probably isn't worth your while, since there probably aren't many people other than me who would particularly want this. But is there any chance you could add a List View mode to the Layers toolbar (ie. no thumbnail - just layer names and numbers)? It would save some horizontal real estate (allowing us to reduce the width by ~100px while still seeing full layer names). It would also allow those of us who use dozens of layers to see them all at once.

---

That isn't a bad idea at all, it will definitely make it easier for managing lots of layers at once.

It seems like Easing object behaves differently on Windows, to be more specific, it's bugged... Since it's open source, could we get a fix?
I believe the issue must be something related to something rounding the math, cause depending on the movement it can get closer or further away...

Quote:

---

Originally Posted by Linky

After the frame rate fix for sub apps other problems started to appear, here is some of which I in countered so far:

- On one of my projects, sub app crashes the whole project

- Timer is out of sync when the main app is on a temp pause (eg. When resizing window or minimizing it)

- when changing the FPS on runtime the whole app freezes (even the debugger)

- when changing sub app size it crash the project randomly (very rare)

---

To add:
- keyboard and mouse: "On any key press" condition doesn't work with sub-apps, I had to use Control X object

Quote:

---

Originally Posted by NaitorStudios

It seems like Easing object behaves differently on Windows, to be more specific, it's bugged... Since it's open source, could we get a fix?
I believe the issue must be something related to something rounding the math, cause depending on the movement it can get closer or further away...

---

I'm pretty sure I've encountered this too.

Another bug in Android:
Sometimes minimizing the app and opening it again causes transparent parts of objects to have a "additive" or "overlay" effect, like the blending mode from Photoshop, similar to some shaders of the same name...
It's just weird, sometimes it can get stuck in this state, it's just a visual glitch, but it can really mess with games that relies a lot on alpha channel...

I'm still on 293.1, but I have a couple of strange behaviors to report & I did not see them listed as fixed in the recent changelogs. Forgive me if they have already been fixed.

1) the expression function random() doesn't seem to be able to generate numbers outside the range 0-65535.

RRandom() is similarly affected. It doesn't generate random numbers outside the range 0-32767

Also, it appears that when referencing a Global String by index, it's using a 1-based index, instead of zero-based like with Alterable Strings of Active Objects. Could anyone confirm this one?

MFA demonstrating above issues. I am on 293.1 though.