and sub-events? possible in fusion 2.5?
and sub-events? possible in fusion 2.5?
Sorry to post here but the Bug-Tracker is not working right now.
I just noticed that in the HTML5-Exporter i can not use the Expression "Read Cookie". I can not get the Expression-Editor to accept the Expression as Valid.
Probably somebody could test with the HTML5-Exporter to confirm this Bug.
Thanks in Advance
jahkri
As soon as Simon is around I will mention the bug tracker issue -- I am sure its just a simple problem with the domain name on the server.
He had to do some upgrades on the server yesterday to keep up with the increasing traffic and it must have done something unexpected.
Thanks Jeff for the Quick-Reply.
I will post the Bug in the Bugbox as soon as it is online again. I just thought i post the Bug here because Yves mentioned on the first Page that it needs to be a Quick-Beta-Test so the Steam-Version can be released quickly.
By the Way, great Update, i realy like the unlimited Variables and Strings
With kind regards
jahkri
Thank you, I confirm this issue, it'll be fixed in the next update.Originally Posted by Jahkri
Not strings yet, only values.i realy like the unlimited Variables and Strings
Yeah if you guys add sub-events I will love you FOREVER.
What do you mean by sub events?
@Simon: This post pretty much explains
http://community.clickteam.com/threads/87214-Should-I-use-Clickteam-Fusion-How-does-it-compare-to-Construct-2?p=633470&viewfull=1#post633470
Yeah, those types of sub events.
Basically just a way to condense down some conditions/actions into easier to digest chunks. Instead of duplicating a lot of conditions that aren't needed, you have a tree structure so that one condition can work with various additional conditions following under it as sub-events.
It seems like a fairly simple thing to add into 2.5 without taking away a ton of Fusion 3 dev time, and it would be a monumental improvement to the event editor...
Like... I mean this would literally change my entire workflow and improve my events 10x over. It just seems more efficient to look at.
It would be exactly the same instructions for Fusion to handle... it would just condense down certain conditions on the user end so it's easier to manage.
Like in the image above, Fusion could still be looking at it like:
Climbing of Active = 0
Repeat while "D" is pressed
Climbing of Active = 0
Repeat while "A" is pressed
Climbing of Active = 0
Upon pressing "Space bar"
Climbing of Active = 0
Upon pressing "C"
But the USER end would only need to see the subevent setup in the image above.
Posting Permissions
Reply With Quote