Fusion (long standing still) annoyances:
1- Pasted event positions itself above an existing event, when it should be below it.
When moving an event to another line number, the event will position itself above the older code, when Fusion reads from top to bottom. It makes sense that any incoming "codes" (be it copied, or moved) should always be (default) to position itself below the older code that was already there.
2- Pasted groups with other group activations within it instead changes its own activations to other activations
or paste only one of the activations even though the other same named groups are present!
Update: it seems the pasted groups problem will be solved in 292.8? I might've understood it wrong! else it is still unbelievable it will get fixed
2 is on the todo list. It's not the issue that will be fixed in 292.8. I tried to fix it in the build 292 but it's not an easy fix, I gave up until I find more time and I know this code a bit better, to avoid breaking even more things.
Physics static movement:
In one of the next updates, would be possible to add Shape of "LAST" image?
Please add blocking function for the toolbars. I always move them by accident and make a mess.
There is also a bug with the magnet function (but it's present still the beginning), if you click on an item them move the mose it will move from it's position even if you released the click. You need to wait like half a second before to move your mouse with no risk. When you want to work fast and select multiple objects whil the magnet function is activated, you will move the objects by accident every time.
I noticed that the Surface object has been updated recently. I'd like to point out that the crash I reported with this object back in 2016 is still not fixed: https://community.clickteam.com/threads/99648-Surface-object-crash. The crash didn't happen in the MMF2 version of the object.
Additionally, I found out that the coordinates for the "Set alpha at XY" action are calculated wrong. If you make an event that does, for example, "Set color at 64,32" and "Set alpha at 64,32", there will be two dots on the canvas with different coordinates.
I was under the impression that the object was abandoned, but since you guys updated it I thought I'd bring this to your attention.
>> I was under the impression that the object was abandoned
The Surface source code is public, I guess anyone can submit fixes for it.
I've fixed the crash, redownload it from the extension manager.
Can't reproduce the issue with set pixel / set alpha at.
Indeed I couldn't reproduce the issue either on the latest version. Thank you for resolving the crash, too.
However, the new version's alpha channel actions appear to be much slower than the version I have on my old build of Fusion 2.5. The stuff I do in my project using actions "Draw line on the alpha channel" (that was previously crashing) and "Draw rectangle on the alpha channel" (which I used as a substitute for the crashing one) take almost half a second on my Kaby Lake i7 CPU now. However, before the update the "Draw rectangle on the alpha channel" action was instant in the same scenario.
I have uploaded an attachment that illustrates the issue. The file "surface_fast.exe" was built using the version before the update. The "Draw rectangle on the alpha channel" action works there and is instant. If you build the same MFA in the latest version, the application will visibly freeze for about half a second. In addition, the behavior of the action in this specific scenario appears to be different. Like, the latest version doesn't seem to do anything with the alpha channel at all in the example.
I also noticed that the EXE built with the older version from the same MFA is about 500KB smaller. Is there a way to reduce the EXE file size in the new version?
I couldn't upload an EXE built with the latest version because it exceeded the forum's attachment size limit.