Build 294.9 - Release candidate

Quote from Volnaiskra

Does this happen to anyone else, or is just me?

I tried your method, but I'm not having this issue myself. Though, I was having an issue with the behavior context menu in the Frame Editor and had to reinstall 2.5+ then 294.9, then reset the context menus in the Toolbar > Customize menu, which fixed my issue. Since your issue is also Frame Editor related, I wonder if what worked for me would fix your issue?

The Application Size Context menu does not respect the current theme (got the same look from 293.10 and ealier)
I's not specific to this build, as I noticed it since the first 294 build I tried, but every time I forget to mention it
Please login to see this attachment.

Quote from piscesdreams

I tried your method, but I'm not having this issue myself. Though, I was having an issue with the behavior context menu in the Frame Editor and had to reinstall 2.5+ then 294.9, then reset the context menus in the Toolbar > Customize menu, which fixed my issue. Since your issue is also Frame Editor related, I wonder if what worked for me would fix your issue?

I just tried resetting the context menus, which didn't fix the clicking issue.......but broke my behavior context menu. So it seems what killed the bug for you brought it to life for me XD. I didn't try reinstalling Fusion/DLC yet though, so I'll do that next. Were you using Steam or standalone?

Quote from Volnaiskra

I just tried resetting the context menus, which didn't fix the clicking issue.......but broke my behavior context menu. So it seems what killed the bug for you brought it to life for me XD. I didn't try reinstalling Fusion/DLC yet though, so I'll do that next. Were you using Steam or standalone?

I use the standalone version.

When you edit a collision test between two objects, and change the current view mode the menu doesn't refresh properly leaving only the first quarter (or less) of the menu rendered, hovering the mouse on an object forces refresh and fixes the problem:
Please login to see this attachment.

OK. I need some feedback about these things I noticed - listed by priority:

1.
It seems in Build 294.9 we can't safely use our .mfa projects which were originally saved in R293.10 and older Fusion 2.5 Builds to build for Android platform
(tested offline with .apk files) - a lot of things are simply not working on Android devices anymore with these older .mfa files.
Only way I found so far to "prepare these projects for Build 294.9" are inconvenient workarounds to get back complete example functionality on Android devices.
It happens with countless older examples with different objects and events I tested - on the device later, some example functionality was always gone.
Please login to see this attachment.
Right above is a test environment with one of my examples that includes some random code, sprinkled with a few useless checks and events.
Test everything in Build 294.9. I originally started to design this shorter .mfa example totally from scratch in Build 293.10 to investigate this special issue.
You know that this specific example is working correctly on the Android device, when it throws many "#" String characters at you, after you clicked the Active object "button" in the Frame (do this quickly or remove the event - end the application in 4 seconds).
If you see no "#" signs at all it's the wrong behaviour. In this example, always check if Data Elements are empty - in this case you must add the "EN.ini" file or no "#" characters are visible even if the example is not affected by the issue.

2.
Picture Editor, here I listed 1 feature request and 2 bugs/things where I'm unsure if this is intentional behaviour or not 1), 2)
Feature request:
-constantly update color tiles and info while LMT is pressed
Bugs?:
-1) Fuchsia pink tile is transparent in Build 294.9
-2) vertical size of these 2 boxes leaves not enough room for the text cursor (accompanied by the glitch that you can draw multiple text cursor instances outside these two boxes) and you can't even visually distinguish what's an E or an F

Quote from Wodjanoi

Picture Editor

Possible Features:
Could you change the default behaviour for palette color box to update
preview color tiles already while pressing mouse button without waiting for mouse button release?

Possible Bugs:
(as you can see here)
Please login to see this attachment.

1) "Fuchsia" pink color is transparent space (for new objects added to the Frame in Build 294.9)
2) both boxes for color input/info:
- Can we already adjust both boxes somehow to make sure that vertical size of each box provides at least enough space to prevent text cursor to stick out at the bottom?
- Here I also noticed, when you place text cursor in these boxes, then click outside, you can draw multiple instances of the text cursor part that's sticking out

Display More

3.
I talked to Fernando and he introduced a specific Multiple Touch object fix for Android - any chance to get this as official bug fix in the upcoming Release Build?
It's the older problem with touch input no longer recognized at all, when specific things in Android OS have been changed by the user and then app is restarting
after it was still running in the background. (this can be easily tested on Samsung devices for example - change resolution, theme, language, etc.)

Wodjanoi about the "Fuchsia" pink color being default transparent, that's intentional.
Originally it was true black (0,0,0), which works well with transparent tools and text tool, but people didn't liked how when they copy and paste images, it would probably make a color they don't want transparent.

First build of 294 actually changed that to bright green, people didn't commented anything, but I suggested to go back to black because text tool and transparent tools would not act well on different colors.
After the switch people said that they actually liked that black wasn't the default anymore lol
So I suggested bright pink, since in most spritesheets it's used for transparent color, and bright green was more commonly used for other stuff.

Which I don't see many people complain, but, as a definitive way to address that and make so people can choose whatever they want as transparent color, a new feature were added:
You can now add to Fusion's Data folder the default image for Active, Backdrop, Quick Backdrop and even Counters. (File should be named for example defaultActiveObject.png)
It will pick the top-left pixel as default transparent color (unless the image uses Alpha Channel, which I don't recommend, or it will default to Alpha Channel mode...)
You can simply export from Fusion's image editor directly to Fusion's Data folder after you're done with the changes and it will be remembered (may need to restart Fusion).
More info on the changelog.

Alternatively, if you're not aware of this, you can double click the transparent color box bellow the palette and choose the transparent color for each particular image.

The Accelerometer object returns the wrong value once Orientation has been changed.

Orientation( "Accelerometer object" ) Expression:
-While in Portrait Mode: Returns 0 (Unknown) when the device is flat, and 1 (Portrait) while upright
-While in Landscape Mode: it Returns 0 (Unknown) when the device is flat, and 1 (Portrait) while upright

I discovered this when trying to set my game's orientation based on the Orientation Value given from the object and I watched my device rapidly change it's Orientation.

accel is zero in flat surface

Please login to see this link.

from this pdf , page 7 bottom

Quote

In a 3-axis accelerometer, it is required that acceleration sensed in the X and Y axes must differ by a minimum amount to sense
when the tilt angle has met a pre-set condition. When the device is placed on a flat surface and the Z angle is 0 degrees with
respect to a line in the direction of the earth’s gravity, there is no way to determine the orientation of the device and the screen
should stay in the last position.

Quote from Fernando

accel is zero in flat surface

The problem isn't it returning "0", the problem is that it returns "1" when the Help File for the object states:

It returns values from 0 to 6 :

--Unknown (should not happen unless you shake the device)
--Portrait
--Portrait upside down
--Landscape left
--Landscape right
--Face up
--Face down

But Landscape Mode is returning "1"

in the image editor, rotating an image also crops it which is a very weird behavior.

if you create a number counter, scale its size and then change the type to "hidden" it wont change the object icon to "hidden icon" anymore, like in previous fuison versions.

Quote from bybyblue

The problem isn't it returning "0", the problem is that it returns "1" when the Help File for the object states:

It returns values from 0 to 6 :

--Unknown (should not happen unless you shake the device)
--Portrait
--Portrait upside down
--Landscape left
--Landscape right
--Face up
--Face down

But Landscape Mode is returning "1"

Display More

is it returning the last?

Quote from Fernando

is it returning the last?

I am not quite sure what you mean by "The Last", but if you are referring to Face Down(6) then, yes, that works.

Edit:
The more I think about, I wonder if the problem is that once the orientation changes, it screws up the values or something.

When navigating the Event List Editor with the keyboard, pressing down arrow on a large event causes Fusion to scroll very slowly and become unresponsive. This slowdown does not happen when pressing up arrow.

In the GIF below, I press the down arrow 5 times. You can see the grey outline move down through the events/comments. When it gets to the large event (#233), it begins scrolling down very slowly, then freezes briefly while Windows shows the spinning circle before eventually highlighting the large event. The time taken to move from the 4th to the 5th event is around 10 seconds.

Please login to see this picture.

Add achievements like in gamemaker.

Quote from bybyblue

I am not quite sure what you mean by "The Last", but if you are referring to Face Down(6) then, yes, that works.

Edit:
The more I think about, I wonder if the problem is that once the orientation changes, it screws up the values or something.

Did you read this document?

Please login to see this link.

Quote from Yves

"Would Active 1 at 100,100 overlap Active 2" tests if Active 1 overlaps Active 2 if it was moved to position 100,100. Is this more clear?

Please see this example.

"Would Active at 100,100 overlap Active 2" would increase the counter if Active 2 closing in Active (even if the objects do not overlap each other).
On other hand, "Would Active 2 at 100,100 overlap Active" increases the counter even if Active 2 and Active are far apart.
What's the difference between these?

Please login to see this attachment.