Build 294.4 - Beta version

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • Hey, so I found this quite some time ago, I basically shared my custom toolbar on the Click Converse Discord server, and apparently it wasn't loading for anyone who tried to import it
    Previously on older builds such as 293.10 it worked, even on heavily edited toolbars, I tested it myself because I had to move to another PC recently
    Here is the toolbar that wasn't working: Please login to see this link.

    I'm still not 100% sure if ALL Custom Toolbars won't import for other users, but it does for that toolbar and some others I tested aswell
    Here is a preview of how the toolbar should look, some parts do change based on the focused editor:
    Please login to see this attachment.

    Game/App developer, artist and a community contributor.
    You can support my work on: Please login to see this link.

  • Quick backdrop set to black (0,0,0) will be displayed as dark red (8,0,0) in frame editor, but it will be displayed as black at runtime.
    Please login to see this attachment.

    Hmm, did you uncheck the "Transparent" option in its properties? There could be differences between frame editor and app running either in DX9 or DX11 mode. I don't recommend unchecking this option, it was initially made for the software mode, was not working in opaque mode in DX9 apps at all, and then might semi-work in DX11 apps.

  • Thanks

    Coming back after a while to Fusion and totally amazed by your recent updates! So I decided to by the +DLC to support Clickteam und even get a few more useful features. :cf25+:
    I absolutely love the new skins and icons, actions, functions. :D


    Some Issues

    Text in the Workspace Toolbar is displyed with the System font.
    The only texts in Fusion as far as I've seen.
    Please login to see this attachment.

    The Colors checkbox in the Application menu editor doesn't follow the bottom border of the window when resizing.
    Please login to see this attachment.

    The No Prefix option in System Boxes is broken. Didn't work in 193.10 either.
    Please login to see this attachment.


    Thanks again for your hard work. :)

    Regards
    Gustav

  • Thanks! The first 2 issues are fixed in the next build. Apparently "No prefix" only works in standard graphic mode, it doesn't work with DX9 or DX11.

  • Hey, so I found this quite some time ago, I basically shared my custom toolbar on the Click Converse Discord server, and apparently it wasn't loading for anyone who tried to import it

    Toobar settings depend on the version of 2.5 you use, you can't import toolbar settings saved with the standard version to a developer version. Also you can't import toolbar settings saved with a version that has the 2.5+ DLC to a version without it.

    I tried importing your configuration to a standard version without 2.5+. Compared with your screenshot, there is one difference, the "Create" toolbar at the bottom just below the Library tolbar is replaced by the menu bar, not sure why. The other bars seems correct.

  • I've managed to isolate a crash to the edittime that was pretty elusive. I had it happen to me a few times and lose a few minutes of progress, but I wasn't sure what it was, now I've got it
    I think it was introduced in 294, I haven't had this before, but can't confirm it was introduced with the update

    If you click too quickly in the event editor / event list editor, its possible to bring up a new context menu element without first clearing the last context menu, which is hidden behind the active frame. When you return to that frame, ie clearing the expression editor or clicking away from that menu, the edittime crashes, presumably because it can't handle the erroneous 2+ context menus. You'll be able to see that ominous background context menu laying in wait and know the crash is incoming.
    Here's a gif of it happening

    Please login to see this picture.

  • Thanks! The first 2 issues are fixed in the next build. Apparently "No prefix" only works in standard graphic mode, it doesn't work with DX9 or DX11.

    Thanks! Okay, that makes sense.

    May it be that the Preferences > Frame Editor > Margins option doesn't work anymore?
    I changed the size but it doesn't seem to have any effect on new applications/frames.

  • Thanks! Okay, that makes sense.

    May it be that the Preferences > Frame Editor > Margins option doesn't work anymore?
    I changed the size but it doesn't seem to have any effect on new applications/frames.

    That setting was always faulty, and was fixed in this version. It used to be that the amount of pixels you entered in the preferences was only properly honoured in 100% zoom, but if you zoomed in it would increase the margin too much (Eg. At 300% the margins would be x3 bigger than your preferences).

    Is it possible that you were used to the old behaviour and that's why it seems to not be working now?

    Please login to see this link.
    My Fusion Tools: Please login to see this link. | Please login to see this link. | Please login to see this link.

  • That setting was always faulty, and was fixed in this version. It used to be that the amount of pixels you entered in the preferences was only properly honoured in 100% zoom, but if you zoomed in it would increase the margin too much (Eg. At 300% the margins would be x3 bigger than your preferences).

    Is it possible that you were used to the old behaviour and that's why it seems to not be working now?

    In my case I didn't use the zoom. The margins are always fixed to 640x480 but the Preferences window contains my chosen values (800x600) even after a restart.

  • In my case I didn't use the zoom. The margins are always fixed to 640x480 but the Preferences window contains my chosen values (800x600) even after a restart.

    Seems OK here, you don't need to restart, the frame editor is updated when you close the preferences. Try with a larger value like 2000 x 2000? Maybe it depends on your screen resolution.

  • Seems OK here, you don't need to restart, the frame editor is updated when you close the preferences. Try with a larger value like 2000 x 2000? Maybe it depends on your screen resolution.

    Okay, it was a misconception. :O
    In all the years I never used this setting. Even if the name says "margins" it was "clear" to me from the beginning that this is the setting for the default size of the frames in a new application. I never scrutinized that. The standard values are 640x480 just like the standard frame size. I find these standard values really confusing. Maybe it's a programmer thing? What does it mean? 320 pixels to the left and right and 240 pixels to the top and bottom? Maybe other starting values would be less confusing. :)

  • I found another small issue.

    If you double-click on the info box (which contains the actions when you hover over a check mark in the Event Editor) you can edit actions directly.
    Sometimes this doesn't work. I tried to isolate it...

    It doesn't work if you create a new application, go to the Event Editor, create a condition and an action for the first time the Event Editor is opened.
    Changing to another window and going back to the Event Editor fixes this issue. This also counts for the following cases below.

    In already existing and freshly loaded applications it shows the following behavior:

    • It works directly if you change nothing.
    • It works if you drag&drop an existing condition as a new one and if you drag&drop an existing action in this new line.
    • It doesn't work if you drag&drop an existing condition as a new one and if you create a new action.
    • It doesn't work if you create a new condition via popup and if you drag&drop an existing action in this new line or create a new action.

    Conclusion: As soon as you insert a new condition or action the first time you opened the Event Editor it doesn't work anymore, even if it worked before. But if you change to another window and back to Event Editor it works as expected.


    Edit:
    Now it occurred more often even after switching back to the Frame Editor.
    But after one quick change again back to the Frame Editor it works again.
    Must have something to do with the editing of actions.

    Edited 3 times, last by Gustav (September 1, 2022 at 12:07 PM).

  • Hmm, did you uncheck the "Transparent" option in its properties? There could be differences between frame editor and app running either in DX9 or DX11 mode. I don't recommend unchecking this option, it was initially made for the software mode, was not working in opaque mode in DX9 apps at all, and then might semi-work in DX11 apps.


    No, it's grayed and impossible to uncheck for me.
    It's working fine at runtime hopefully, the only issue is visual in frame editor.

  • I found another small issue.

    If you double-click on the info box (which contains the actions when you hover over a check mark in the Event Editor) you can edit actions directly.
    Sometimes this doesn't work. I tried to isolate it...

    Weird problem, it's fixed in the next build but I don't understand why this happens and why the fix works. :p

  • Weird problem, it's fixed in the next build but I don't understand why this happens and why the fix works. :p

    XD


    I would also like to talk about some UX cases.


    The new Toggle Event List mode command :cf25+: is really useful but has one big downside.
    It clutters the navigation history (Back & Forward buttons in toolbar). Every time I press the toggle button or use Ctrl+T a new navigation entry is added.
    In my opinion this circumstance makes the navigation obsolete if I use the toggle button frequently. To go back to the window before, I have to press Back as many times I toggled the windows.
    Of course I can press the Back button after using the toggle button but if I do so: what would be the point of the toggle button? So I could use the other editor buttons right away.
    So maybe it's a better idea to exclude the toggle button from the navigation history. But that could be confusing too.

    A possible solution could be to add an entry in the navigation history only if the window Fusion would jump to is different from the second last history entry (Event Editor or Event List Editor).
    I don't know if I described it okay. Let's say the following list represents the navigation history, the newest entry at the bottom:

    • Storyboard Editor
    • Frame Editor
    • Event Editor


    If I press the toggle button now an entry Event List Editor will be added at the end. If I press it again Fusion finds that the second last entry is Event Editor so it doesn't add it again to the end. It just deletes the last entry Event List Editor. Now I can press the Back button and jump back directly to the Frame Editor. :)
    I think this would be a plausible solution because the toggle button is different from all other editor buttons and visually represented as "option/check" which changes appearance when in Event List Editor.


    Speaking of navigation history, there is a small issue. As far as I can see the Storyboard Editor button is the only one which keeps adding entries to the navigation history every time it's pressed. Press it ten times in a row and ten entries will be added.


    Another UX case is the option to open the Expression Editor via keyboard.
    I like to work with the keyboard as much as possible and there are some really essential "shortcuts" missing in my opinion.
    In the Frame Editor, Frame List Editor and Action Editor one is able to move the selection mark with the arrow keys. One can copy, cut and paste and select conditions and actions (via spacebar) using the keyboard. But it is impossible to open the Expression Editor of an existing action for example. I always have to take my mouse, move it over the action and double-click on it. After editing an action I move intuitively the selection mark by pressing the arrow keys to the next action I want to edit and press Enter - but nothing happens. Often I just have to change a value and close the Expression Editor again using Enter. But this "flow" is interrupted by the missing option to open the Expression Editor with the Enter key.

    It would be really helpful if one would be able to press Enter to:

    • open Expression Editor for Actions
    • open Expression Editor for Conditions
    • activate the New condition button


    Puh... that's all for now. Thank you :)

    Edited once, last by Gustav (September 2, 2022 at 12:52 PM).


  • Another UX case is the option to open the Expression Editor via keyboard........It would be really helpful if one would be able to press Enter to:

    • open Expression Editor for Actions
    • open Expression Editor for Conditions
    • activate the New condition button

    There actually is keyboard support for those things. In each case, the key combination shift+enter, down, enter will achieve what you want. This is a somewhat cumbersome key combination, of course, so you'd be best off using a macro program like Autohotkey to map it to a simpler key combination. Incidentally, there are Please login to see this link. you can improve your Fusion experience with Autohotkey.

    Please login to see this link.
    My Fusion Tools: Please login to see this link. | Please login to see this link. | Please login to see this link.

  • There actually is keyboard support for those things. In each case, the key combination shift+enter, down, enter will achieve what you want. This is a somewhat cumbersome key combination, of course, so you'd be best off using a macro program like Autohotkey to map it to a simpler key combination. Incidentally, there are Please login to see this link. you can improve your Fusion experience with Autohotkey.

    Thanks for the tips! Will have a look. Learning something new every day. X)

    A built in more direct way like simply pressing Enter would be great. Enter doesn't do anything else in the editors it seems.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!