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.
  • Every time I see the condition "never", I always think to myself that it looks really useful, but I'm yet to ever use it (I guess my motto is 'never say never', har har har). Do you guys use it, and if so, how?

    Please login to see this picture.

    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.

  • I mainly use it to temporarily deactivate an Event when i test my Application.
    Im unsure if the Never condition can actually prevent Actions from triggering, but would be fun to check if this is possible

    How can i change username and display name?
    Please login to see this link.

  • Never ever I used never, I didn't pull this useless lever. XD
    No - I mean, you have the convenient possibility to toggle events on and off with groups, which makes this condition primarily a good supplement.

    Currently working on ... [SIGPIC][/SIGPIC] ... a Puzzle Platformer

    Edited once, last by Wodjanoi (March 30, 2017 at 11:38 AM).


  • Im unsure if the Never condition can actually prevent Actions from triggering, but would be fun to check if this is possible


    I just assumed it did. But actually, I just tried this, and it didn't work as I expected:

    Please login to see this picture.

    I expected that event #3 would prevent the application from closing in #4, but no, it still closes. So what does never actually do?

    EDIT: according to the help file:

    Quote

    Never inserts a blank event line in the Event editor of your application. All of the actions inserted on this line will never happen during application runtime.

    I think a reasonable understanding of that second sentence would expect that event #4 above wouldn't trigger. But it seems like never merely nullifies that particular event. If so, that's a misleading name IMO. It really should be called something like don't, null, or maybe later ;)

    Oh well, I guess it's back to never saying never...

    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.

    Edited 4 times, last by Volnaiskra (March 30, 2017 at 1:33 PM).

  • Everyone saying it's meant to be used only to temporarily disable event lines is absolutely correct. This was NEVER meant for making logical code, ONLY to disable a line for the sake of debugging etc. Now that you can actually disable and enable lines its completely redundant.

  • I use Never for debugging stuff.

    Step 1: Create an event to test out a feature
    Step 2: When you no longer need that event, I put in the Never
    Step 3: Leave that there in case I ever need to test that out again, remove the never status when I do.

    SUPER helpful.

  • I think it is useful to hold templates of event blocks that you do not want to delete. But dont want to execute. Another alternative to disabled groups.

    I would rather keep it than remove it. I find myself using it more than deactivate because it is fast and I can keep easily see what should never run.

  • its 100% redundant. you can now deactivate single lines, not only groups. so the theory of seeing events you dont want to delete is shot to pieces. you can do that without using NEVER.
    having said that - its not harming anyone being there.

  • its 100% redundant. you can now deactivate single lines, not only groups. so the theory of seeing events you dont want to delete is shot to pieces. you can do that without using NEVER.
    having said that - its not harming anyone being there.

    True.

    BUT, Unlike simply activating/deactivating lines, you can search for events using the "never" condition. So thats ONE advantage

  • You can change the Fusion skin to make it easier to find your de-activated lines. Mine show up with a red tint so I never miss them whenever I scroll my list.
    Please login to see this picture.

    To change this simply open and edit the info.ini within the "Clickteam Fusion\Skins\NameOfSkinHere\" folder. It's filled with all kinds of stuff you can mess with.

    Please login to see this link. Please login to see this link.
    Freelance Dev | Currently Working on Jarvis | Please login to see this link.

  • Did not know this!

    Though I still think the search option would be better for bigger, even massive projects. I often have groups within groups within groups within groups within groups within...

    I get lost in my own code sometimes.

  • Well, this thread has actually taught me a very handy use for "never".

    I always use "inactivate/deactivate", but the problem with that is if you have single events deactivated inside a group, and then you deactivate & activate that group, all events in that group become activated, even if they were previously deactivated (not sure if this is a bug or a feature). Which is a problem, especially if you can't remember exactly which lines were activated and which weren't.

    So now at least I know I can use "never" for events that are inside a group that I'm about to deactivate, knowing that they'll continue to be switched off even after I reactivate the group.

    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.

  • Also, search won't find things in collapsed groups within groups. To make things worse, there is a bug in the ELE where the Open All Groups command doesn't open all nested groups. So doing a search on a big project becomes even less reliable.

    Please login to see this link.

  • Do I smell a bug box feedback request for filtering De-activated Lines? :D

    Please login to see this link. Please login to see this link.
    Freelance Dev | Currently Working on Jarvis | Please login to see this link.

  • Also, search won't find things in collapsed groups within groups. To make things worse, there is a bug in the ELE where the Open All Groups command doesn't open all nested groups. So doing a search on a big project becomes even less reliable.

    Yeah, for both those reasons, using a hotkey for Open All Groups is a must. I'm in the habit now of hitting it several times in quick succession to actually open all groups (because it eventually opens all groups when you do that)....and also doing that before every search. Both are annoyances, to be sure, but it just becomes muscle memory after a while. But if you couldn't use hotkeys (which IIRC you couldn't until about a year ago), it would be murder.

    Though if I remember correctly, you use a keyboard-less wacom setup, so I guess hotkeys wouldn't apply in that case :/ They really should fix the open all groups bug. The weird thing is that Photoshop has had basically the same bug for years.

    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.

    Edited once, last by Volnaiskra (April 2, 2017 at 2:52 PM).

Participate now!

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