Printable View
Something that irritates me from time to time is that when you build your application you always gets prompted by an "do you want to save your changings" dialogue when closing MMF afterwards. Nothing has changed. I haven't even touched the frames. Just built an app. But i get asked if i want to save the changings. I would call it a bug :)
Yeh, that does kinda' get on my nerves after a while. Since I have to build my application like every 5 minutes to test it XD
Why do you have to build it to test it?
If you change the build filename, the application is marked as modified (as the build filename is saved in the properties).
I guess I will offer my opinion also. The save function is for the programmer's protection. Annoying or not it is a nice feature.
Marvin
Whenever you launch a build, MMF will then think that a change was made to the app. There's no need to change the build filename for that. I find it a bit annoying too, but only a bit. :)
And that's the point. Even when just a bit annoying it is annoying ^^
But i change nothing. I open my project, build my app, close MMF, and voila, i get asked to save changings that didn't happen ...Quote:
If you change the build filename, the application is marked as modified (as the build filename is saved in the properties).
I'm never been bothered by this, but that might be because I save constantly... Habit from the old TGF days where the program crashed every 10 minutes...
As told, i don't do anything at the mfa. I open it. Then i immediately choose Build/Application, build my app. And gets promted to save changings when closing MMF.
Err... sorry, I can't reproduce it... I create an application, save it as app.mfa, build it, save it again (as I've modified the build filename) and then close it, reload it, select "Build" without modifying the build filename and close MMF2 : it doesn't ask me to save the application...Quote:
Whenever you launch a build, MMF will then think that a change was made to the app. There's no need to change the build filename for that. I find it a bit annoying too, but only a bit.
I can't seem to reproduce it either with a blank app. But I can assure you that with the app I'm currently working on it happens. I'm experiencing the same thing than Tiles, I just need to open my app and immediately build it (by overwriting the previous .exe - no change in build filename). I don't even need to open an editor.
When the build is finished, MMF will display an asterisk near the name of my application. MMF thinks I made changes.
Not a very big deal though. :)
Could you send me your app? (or at least a single frame if you can reproduce it even if you remove all the frames)
When I build my application, it askes me to save after it every time. I though that was normal, and I can't see what difference it would make at all.
I have the feeling that you don't understand the problem. Just to show the problem and that we know what we talk about here, here comes an SWF movie about it, 320 Kb:
http://reinerstileset.4players.de/ext/savechangings.swf
As told, nothing dramatic, but nevertheless ... :)
I can confirm this bug. It only happens with some of my applications, Knytt Stories being one.
Some applications automatically becomes marked as 'changed' as soon as they are exported (even with the default export filename) and other applications does not. I haven't been able to find the cause.
Yes the same here only with some applications too.
Ah, forgot to add, all i did was throwing in an active into the frame of a fresh app, then saved the app and closed MMF. And on as shown :)
thats odd, that happens to me as well what the guys are saying. No need to do anything, if you build it without changing anything, it gives an asterix like i did something to modify it.
When you run the video notice -- at first there is nothing in the Build filename property.
You build an application then notice a file name is in that location.
Now if you save your MFA and close it
Re-open it and see if the build filename exists and rebuild your application this time when you close MMF it will not prompt you to save your MFA.
The reason (I think) MMF is asking you if you want to save is because you have made a change the first time -- You changed the property under the filename from nothing to what you built.
Imagine the screaming is MMF didn't prompt you to save the source when the properties change.
I see what you mean. But i haven't touched the properties, i haven't touched anything besides build file. I have output a file. And can simply not see how this could change a property of the mfa. And i ALWAYS deny saving anyway. I have not changed a bit. And i don't want to change anything neiter. That's why i have saved it before i build the app.
But i nevertheless have to click the dialogue away.
Imagine you open a file in Wordpad to read its content. Let's even save the file under another filename. You don't change anything, but Wordpad would ask you then to save your changings all the time. See the point? :)
Then let it be the bug that building an app changes the mfa.
The first time you build an application it will update that property.
Once you save your MFA with that property in place future opening of the file and building will not produce the save as dialog unless you change the property.
You are changing a property thats why MMF is prompting you to save.
The property is updated when you give your build exe a name.
Future building under the same name will not prompt you to save.
I will upload a video if you want
I give up. All i can do is report the bugs. Decision to fix it or to declare it to a feature is in your hands :)
Why?
That property is updated when you build your application.
Try it
Its not a bug a property was changed.
I see, it`s a feature. Every time i build something the mfa changes, recording the path.
But for me it makes completely no sense to store the build app path in the mfa. You have a save dialogue there anyway where you choose to save your app then. And normally you build your app once. Which means there is no need to use a formerly stored path in nearly 95% of all cases. I nevertheless get forced to save my app again then.
What would make sense is to store the last paths in MMF as it happens to the last opened mfa.
Looking closer at that, what i am absolutely not happy about is that a path with my file structure is saved within my mfa. Dangerous feature.
Okay the very first time you build an app the 'Build Filename' property is updated, a change was effectively applied to the app. Sounds normal.Quote:
Originally Posted by Jeff
But thereafter every future building under the same name will also apply a change to the app. And I think that this is not normal.
As said earlier it doesn't happen with every app. And I couldn't isolate the problem yet, whether it comes from a particular setting or object.
EDIT: I can't believe this thread is already 3 pages long! :D
Proof that it is somehow an interesting issue ;)Quote:
EDIT: I can't believe this thread is already 3 pages long! \:D
I tried it, observating very close what's going on. And it seems that when you save it with the changed buildpath, then in future tries build in the same path, you don't get prompted to save changings. Haven't noticed this before.Quote:
But thereafter every future building under the same name will also apply a change to the app.
Now that we discuss about this issue I would nevertheless suggest not to store the buildpath in the mfa for told reasons.
Prior to removing all the frames, I have removed all the code contained in the Global Events Editor. After that the problem didn't occur anymore. So it has probably something to do with the Global Events Editor? To the other people experiencing the problem, if you have some code in the Global Events Editor, could you please try to remove it and see what happens?Quote:
Originally Posted by Yves
I get prompted after every build, even if don't do anything. I don't really get prompted, MMF sticks an asterisk near the name of my app in the Workspace Toolbar.Quote:
Originally Posted by Tiles
I've also noticed that the asterisk appears as soon as I open the Global Events Editor, and as soon as I check the External Files or Extensions tabs of the Data Elements. So weird.
Personally I wonder what's the problem here, wasting about half a second of your life every time you close MMF2? There have been popping out lots of bug raports lately, but I think this shouldn't make any difference. I find it even more comfortable myself when it asks to save changes after building my app even though that didn't have any effect. I can see that if CT changed this there would be posts about why it doesn't prompt to save :)
My app is huge and MMF needs about 5 seconds to do the saving. Of course the solution here is to simply ignore the prompt. But Yves could probably spend his time better, on more important stuff. :)