Extensions vs. Sup-Apps

[ProdigyX]

To those extension developers, have your extensions ever acted strange with sub-apps in the application? I've written a character extensions from EDIF (character as in letters). The extension does not involve anything with sub-apps. Keeping this in mind, I ask for possible resolutions to the following problem.
When the sub-app is on frame and active (pop-up dialog sub-app) conditions from the extensions do not register. Furthermore, when exiting the sub-app, the entire application force closes. I've tried nearly every combination of sub-app, frame, and application properties and I cannot figure out what is going on.

Below are the extension and .mfa

MMF2 Extension
https://dl.dropboxusercontent.com/u/...ct%20Error.zip

MFA Demonstration
https://dl.dropboxusercontent.com/u/25332369/Weird.mfa

How to see issue:

1. Run Frame (not entire app)
2. Observe the counter counting up
3. Close Frame
4. Run Application
5. Observe the counter stays at 0
6. Close Sub-application
7. Observer entire application crash

If anyone has any guess as to what might be up, do reply

[LB]

You should not have spaces in the MFX name, this makes it completely impossible to port it to other runtimes (I'm not kidding)

For me, the application crashes when exiting the sub-app, it doesn't "force-close".
Also, just running the frame, the counter does count up.

My best guess is that you have done something to corrupt the state of your object.

How old is the version of EDIF that you are using? You have enabled alterable values, but in older version of EDIF this required some manual changes to the run data structure.

Can you upload the source of the extension?

[ProdigyX]

Duly noted about spaces in mfx names

Forgive me, that is what I originally meant about crashing. (did not mean to say force close)
With regards to just running the frame that is what I said. It only does not count up when the sub-app is open (like when running application). When this happens ANY action for the event causes a crash. If there are no actions, the app goes on just fine.

This EDIF version is from the CT github is from March, specifically March 23 of this year.

Source can be found immediately below. Keep in mind that I am using VS 2012.
https://dl.dropboxusercontent.com/u/...-%20Source.zip

Would it be possible for the problem to stem from the properties of the extension? I managed to work out how to do properties in EDIF so I put in a few properties.

[ProdigyX]

Update:

This same problem happens to all of my EDIF extensions. They are all made using the same March 23 EDIF file. One is a timing extension while another is a mathematical extension, while the extension posted above is the only one with properties. The only other similarity that exists is they all have AVs. For the AVs, I simply added the "OEFLAG_Values" in the Extension.h. Outside of this nothing was done for AVs. Building the extension without AVs appears to have no affect on the problem however.

Update 2:
This problem only occurs when the sub-app refers to a frame inside the app. When other .mfa or .ccn files are used in the sub-app, the problem no longer exists.

[LB]

The only other similarity that exists is they all have AVs. For the AVs, I simply added the "OEFLAG_Values" in the Extension.h. Outside of this nothing was done for AVs.

In that version of EDIF you also have to uncomment the appropriate lines in the Run Data structure- you need rCom and rVals for MMF2 to use.

Building the extension without AVs appears to have no affect on the problem however.

Are you sure? Either uncommenting the lines or not having AVs makes it work for me. Make sure you create a new MFA, don't use the old one.

[ProdigyX]

With regards to the rCom and rVals

struct RUNDATA{
//Main header
headerObject rHo;


char r //Placeholder for the optional structures
[
sizeof(rCom)+
sizeof(rMvt)+
sizeof(rSpr)+
sizeof(rVal)
];
//Pointers to the optional structures, null values mean that that OEFLAG was not specified.
rCom *rc; // Common structure for movements & animations
rMvt *rm; // Movements (OEFLAG_MOVEMENTS)
rSpr *rs; // Sprite (displayable objects) (OEFLAG_SPRITES)
rVal *rv; // Alterable values (OEFLAG_VALUES)


Extension * pExtension;
};

That is what my RunData struct looks like. Unless I am mistaken; this should be correct with regards to the AV, but I should comment out the movement and sprite flags yes? If should I also comment out the respective fields in char r?

char r //Placeholder for the optional structures [
sizeof(rCom)+
sizeof(rMvt)+
sizeof(rSpr)+
sizeof(rVal)
];

Alas having not AVs and using a new .mfa does not change anything, but this could be from certain lines from above not being commented out.

[LB]

Ah, you mean March 2013, I thought you meant March 2012. In that case, leave your rundata struct alone. I'll do some testing to see what's up.