Build Application crashes when trying to run a sub-application

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.
  • When I build my application and run it, it crashes as soon as it reaches an event that creates a sub-application. It only does this if it is built; when I run it within MMF, it works perfectly fine. I have tested as many things as I could come up with but have reached no solution. Perhaps some of the following information will allow someone out there to help me:

    -If I uncheck "Compress the runtime" under the application's properties (Build Options), I get the following message when I build and run the application:
    "EDIF SDK - Error
    Function.json not found!"
    I do not get this message if I compress the runtime, however, and re-installing the Function object had no apparent effect. (I used ExtentionView to install it.)
    -The sub-applications are all frames from the application (they are not separate applications)
    -The Function object (which I assume is the subject of the error mentioned above) is not present on Frame 1 or the frame of the sub-application causing the crash.
    -There are various sub-applications in this application, and they all cause the crash. I tested this by adding an event that created a sub-application "Upon pressing 'Space bar'"; the program invariably crashed when I hit the space bar, no matter which frame the sub-application ran or which sub-application object I created. The only exception to this is if I made the sub-application frame "Frame 1" (the same frame that creates the sub-application), in which case the application doesn't crash and actually goes on to complete the event "Application [Sub-Application] is finished." (It may be inherent in the sub-application object to not run if it tries to run the frame that created it, I'm not sure. I was getting desperate!)
    -In fact, if I have the sub-application "Create at start" (under Properties>RunTime Options), the application doesn't even run when I hit "build and run." It shows the progress bar that indicates it being built, but then nothing happens when it is finished. If I just build the program as an Application and then double-click on it to run it, nothing happens then either.

    Let me know if you need any other details or attachments. If I find anything else out, I'll be sure to post it as well.

  • This certainly is strange Arnax, I have been working on an MDI app the last few months and haven't had this problem thus far.

    Are you running the latest BETA version?

    Game Launcher Creator V3 - Please login to see this link.
    Bespoke Software Development - Please login to see this link.
    Learn Clickteam Fusion 2.5 - Please login to see this link.

    Danny // Clickteam

  • Sure. A brief background on the application: My brother and I created a HomeworkHelp Website a few years ago where people could go to form study groups, view flashcards, and use study guides we made and uploaded. These study guides were primarily made using the Quiz Object in MMF2, which worked pretty well but wasn't quite as easy to customize as we would like and, more importantly, guide creation was limited to a very small handful of people who had MMF2. Thus, I set out making this application last summer in order to allow other people have access to a user-friendly guide generator, with which they could contribute to the site by making and uploading guides (through the application).

    Since the MFA file is too large to upload, here is a link to download it instead (through Dropbox): Please login to see this link.

    Also note that the application will create a few files in its directory, so you may want to isolate it in a new folder somewhere (like your desktop).

  • The crash happens in the Function object, apparently when it tries to load an image. Perhaps an error of an old version of the EDIF SDK. You should tell the author of this object to recompile it with the latest version of EDIF, that could fix the problem.

  • When it loads an image? I'm not sure what image it would be loading.... O.o

    I talked to the author of the Function Object and he told me he already recompiled the Function Object so I did some more testing, and now I am even more confused than before. It does appear that the Function Object could be the cause of the crash, but I don't know if it is the object's fault or MMF2's fault. First of all, as I already mentioned, the Function Object isn't even present in frame 1 or the frames I use for sub-applications, yet this is where the crash occurs. Secondly, and even more perplexing, when I tried deleting all instances of the object from my application, it inexplicably kept reappearing (at least on one particular frame). I would delete it, go to a different frame and come back and it was back! It appears that deleting it didn't actually delete it, because all the events were still there and everything - only the image of the Function Object was deleted. O.o Anyway, I tried deleting that frame and now everything runs normally, except of course when the application is supposed to run that frame. What the heck is going on?? Eliyaha (the author of the Function Object) says it sounds like a corrupt .mfa and suggested I had you (Yves) or Francois investigate.

    (Just in case you want to look back at my application, the frame in question is Frame 8 - Review My Guide, most of which I copied from a separate application I made.)

  • Ok, well after more desperate testing, I have come across more bizarre results. I was able to somewhat reproduce the crash in a new application with only 3 frames (one to create a sub-application, one to act as the frame for the sub-application, and the third being the frame from the original application that seemed to have part in the crash [frame 8, mentioned above]). So I copied my application so that I could test some things without permanently ruining it, and tried deleting all the frames besides those 3. The crash still occurred. Well good, I thought, that means I'm getting closer to finding the solution.

    That's where the most bizarre part comes in: I was more correct than I ever would have anticipated, because when I put the rest of the frames back in, the application mysteriously started working! Ok, I lied - that's not the most bizarre part. The most bizarre part is that when I went back to the original application (because, remember I copied it to test) and did the same thing, it still crashes. So it seems that my copy may turn out to be my actual application...and I'll just pray it keeps working because I have no idea why it would be.

  • Actually, I think I know why it works. I was able to get rid of the function object by deleting it AND all actions that created it (which I had put in to fix some other problem, although I don't think it's there anymore...let's hope). So the problem was still somewhere in a disagreement between the Function Object and MMF2 I reckon, although I can't imagine why no one else has brought this up before.

  • So I guess that still doesn't really help me...because I still need the function object the way I set it up. :/ Unless I go back and change it all, assuming that would even fix it...lot of effort that could easily be for naught. :(

Participate now!

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