Build 294.14 - Release version

Quote from BenjaminG

Hello Volnaiskra, Yes, Yves solved the issue (back in july 2022, so the fix should be in the Last stable release).
As far as I remember it was a bug in the editor that was not causing project corruption.
And I didnt encountered this bug since the last build.

Thanks for replying. Very relieved to hear it didn't cause corruption! I've been working with the same qualifiers for a few more hours, and I haven't seen the error again. I'm using 294.14, so I guess I just stumbled upon a rare not-yet-squashed version of the bug. But if it's just an editor glitch, I'm not too worried.

Heyo,
The WebView2 help file (from Manager or Fusion build) is broken, none of the inner pages load.

There's a working one on the Darkwire mirror.

Can you amend the "Find" results that say "xxx was not found in the events", to "was not found in the visible events"?

Please login to see this picture.

Would it be possible to introduce an option that allows selected layers in the Frame Editor to be invisible? Currently, clicking on the eye button of the currently selected layer doesn't do anything. I often find myself wanting to quickly toggle the current layer's visibility - either to see what's behind it, or as a way of seeing what's on the layer itself (by seeing what disappears when I hide it). But the process is needlessly convoluted for something that should be really quick and simple:

1. You want to hide the visibility of layer (A), but you realise you can't because it's the current layer
2. So you click on a different layer (B) so that A is deselected.
3. You hide the visibility of A
4. You realise that by selecting B, you've just inadvertently made it visible, because it was invisible before, but Fusion automatically shows any layer you select.
5. You want to make B invisible again like it was supposed to be, but you can't now, because now it's selected, so now hiding it is forbidden.
6. You start looking around for some other layer you can temporarily click on just so that you can re-hide B. You need to be careful to find one that's currently visible because you don't want to make the same mistake again.
7. You find another layer that's not currently invisible (C) and click on it
8. Now you can finally re-hide B.

The above annoyance would be eliminated if Fusion would just let any layer be visible or not, independent of whether or not it's selected. This is not unorthodox behaviour: lots of programs work this way (eg. Adobe programs like Photoshop, Illustrator, After Effects). Even the Fusion event editors work this way, allowing you to deactivate selected events, or select already deactivated events without forcibly activating them.

So my request is for something like a "allow selected layers to be hidden" option in the preferences. This would have two effects:

1. the eye button would successfully toggle the visibility of a currently selected layer
2. selecting a new layer would no longer forcibly show that layer if it was previously hidden.

Is there any option to add a shortcut to File>Build>Application? In View>Toolbar>Customize I really can't find under "File" menu.

Quote from SevenSails

Is there any option to add a shortcut to File>Build>Application? In View>Toolbar>Customize I really can't find under "File" menu.

Yes, it should be the one visible in the screenshot below.

Please login to see this attachment.

Quote from Tek

Yes, it should be the one visible in the screenshot below.

Please login to see this attachment.

Got it, thanks!
I didn't make the connection between File and Application without the "build"

Heyo, the WebView app cache Please login to see this link. from Android WebView, so Android apps with WebView no longer build in Android API 33.

> Task :app:compileDebugJavaWithJavac
C:\Users\Phi\AppData\Local\Temp\AndCAF1.tmp\app\src\main\java\Extensions\CRunWebView2.java:1336: error: cannot find symbol
			myWebView.getSettings().setAppCacheEnabled(true);
			                       ^
  symbol:   method setAppCacheEnabled(boolean)
  location: class WebSettings
C:\Users\Phi\AppData\Local\Temp\AndCAF1.tmp\app\src\main\java\Extensions\CRunWebView2.java:1337: error: cannot find symbol
			myWebView.getSettings().setAppCachePath(webAppData);
			                       ^
  symbol:   method setAppCachePath(String)
  location: class WebSettings
C:\Users\Phi\AppData\Local\Temp\AndCAF1.tmp\app\src\main\java\Extensions\CRunWebView2.java:1338: error: cannot find symbol
			myWebView.getSettings().setAppCacheMaxSize(8*1024*1024);
			                       ^
  symbol:   method setAppCacheMaxSize(int)
  location: class WebSettings

Instance Value Bug:

-Ctrl-drag an object in the Frame Editor to create a duplicate
-The duplicate becomes selected, while the original is deselected (this is good)
-With the new duplicate still selected, change the Instance Value to 999.
-Click outside the object to deselect it.
-Now inspect the duplicate and the original. The original will have an Instance Value of 999, while the duplicate will not. It should be the other way around.

If it's not too much work, it would be great if in Data Elements we could include subfolders and its files instead of having to go one by one in the subfolders and select all files. It gets tricky to keep track of what is included and what is not when you have more than 90 folders to include.

Please login to see this picture.

UI - design questions / request

1)
Generally it's not clear to me why this very first line/divider element directly under the Window title(see above screenshot: fuchsia color) - only pops up for the Main Toolbar if it's currently the very top row?
With the recent UI adjustments I thought now the main purpose for this horizontal divider is for the accessibility - that it is visually easier to avoid that you accidently open the general window options if you quickly plan to open |View - Toolbars →| per right click.
In this case it's a bit strange that this divider element disappears when a different Toolbar row maintains the top position, isn't it?

2)
I think it's a regress that "Toolbar blocks" are now visually separated from each other only by the "move around/detach handle".
If it's no diffcult task - could you eventually bring back the horizontal(Toolbar block's lower edge) + vertical(Toolbar block's right end) divider elements from before?
I noticed 1-2 reports of other people who can't cope with this specific change in the UI design and for one person it was the only reason to completely stay away from Build 294.3+
Why do you have actually taken this design decision I wonder? One logical reason I see could be to better show that vertical position adjustments of movable Toolbar elements/rows are allowed.
It doesn't appear of such importance to suspend the previous divider behaviour in consequence though.

Hello, I realized something :o

When there are many conditions The "Action Info" appears very displaced from the position of the mark.

Please login to see this attachment.

The greater the number of conditions the distance becomes greater, if there are many conditions the "action info" disappears from the screen

Quote from Wodjanoi

Please login to see this picture.

UI - design questions / request

1)
Generally it's not clear to me why this very first line/divider element directly under the Window title(see above screenshot: fuchsia color) - only pops up for the Main Toolbar if it's currently the very top row?
With the recent UI adjustments I thought now the main purpose for this horizontal divider is for the accessibility - that it is visually easier to avoid that you accidently open the general window options if you quickly plan to open |View - Toolbars →| per right click.
In this case it's a bit strange that this divider element disappears when a different Toolbar row maintains the top position, isn't it?

2)
I think it's a regress that "Toolbar blocks" are now visually separated from each other only by the "move around/detach handle".
If it's no diffcult task - could you eventually bring back the horizontal(Toolbar block's lower edge) + vertical(Toolbar block's right end) divider elements from before?
I noticed 1-2 reports of other people who can't cope with this specific change in the UI design and for one person it was the only reason to completely stay away from Build 294.3+
Why do you have actually taken this design decision I wonder? One logical reason I see could be to better show that vertical position adjustments of movable Toolbar elements/rows are allowed.
It doesn't appear of such importance to suspend the previous divider behaviour in consequence though.

Display More

my eyes watered when i read that, and my brain switched off... i've always and still have done up to the last update, just re organized my tool bar into a simple one that uses the features i use all the time. its completely customizable.

Hello! I need help!
I use fusion on a mac via wine. now in version 294.14 everything looks extremely ugly. how to return the previous view of windows and toolbars, as it was in earlier versions?

294.14 ugly
Please login to see this attachment.

292.29 beautiful
Please login to see this attachment.

pls help!

Quote from endloz

Hello! I need help!
I use fusion on a mac via wine. now in version 294.14 everything looks extremely ugly. how to return the previous view of windows and toolbars, as it was in earlier versions?

pls help!

Version 294 includes a new UI engine, so many parts of the interface look different. However, on your system many of the icons are clearly broken, which is not supposed to happen. 294 includes a new panel called the Skin editor toolbar, which lets you edit most aspects of the interface, so maybe try changing some things in the Skin editor toolbar and seeing if that helps.

Quote from Volnaiskra

Version 294 includes a new UI engine, so many parts of the interface look different. However, on your system many of the icons are clearly broken, which is not supposed to happen. 294 includes a new panel called the Skin editor toolbar, which lets you edit most aspects of the interface, so maybe try changing some things in the Skin editor toolbar and seeing if that helps.

Thanks for answer. I looked at the Skin editor toolbar, but it did not give me a positive result. Tell me please how to disable the new UI engine and return to the old view?

Quote from endloz

Thanks for answer. I looked at the Skin editor toolbar, but it did not give me a positive result. Tell me please how to disable the new UI engine and return to the old view?

For that, you would have to uninstall 294 and install 293. With Steam, that could be tricky, since Steam automatically updates

Try completely uninstalling and reinstalling 294 in case something was bad about the installation.

Quote from Volnaiskra

For that, you would have to uninstall 294 and install 293. With Steam, that could be tricky, since Steam automatically updates

Try completely uninstalling and reinstalling 294 in case something was bad about the installation.

I've reinstalled steam and fusion three times, but it doesn't help. All other versions work very well, but version 294 with the damn new UI engine looks really bad. Essentially I have to use a lame product. I know that many scolded fusion for its outdated interface, but I really liked it, it was cozy.
Why is it not possible to opt out of using this new UI engine (for example, some kind of switch in the settings)?

tradesman blaming the tools as usual.

Quote from danjo

tradesman blaming the tools as usual.

What is the use of this message?

Guys please tell me what else can be the solution to the existing problem with the interface?