MMF2 Build #249 - Beta #4

Aha! Just found the bug.

It happens when the layers are deactivated. I created an application with five layers.

LAYER 5 (DEactivated)
LAYER 4 (ACTIVATED)
LAYER 3 (DEACTIVATED)
LAYER 2 (DEACTIVATED)
LAYER 1 (DEACTIVATED)

I created two actives (Object 1 and Object 2) and placed them on layer 4)

Then this event was created

TIMER = 2 SECONDS:
Create "Object2" relative to "Object1" at (0,0)

Then in the event editor I just EDITED that condition (I didnt copy or delete, just edited), so that when selecting an object to position I selected the child object again - ie.

TIMER = 2 SECONDS:
Create "Object2" relative to "Object2" at (0,0)

This then creates the object on Layer 1 and causes the bug. Any condition that creates an object causes this bug, not just the timer reaching 2 seconds.

Hope this is helpful.

Hmm... I cannot reproduce it in a fresh application, I must have missed something... Thanks anyway!

I found a small unhandy issue in the File object, maybe you want to fix it.


Say there is only a folder (no file) named C:\folder on our system:

Name exists > C:\folder > [color:#009900]true[/color]
Name exists > C:\folder\ > [color:#009900]true[/color]
Name is a file > C:\folder > [color:#009900]false[/color]
Name is a file > C:\folder\ > [color:#009900]false[/color]
Name is a directory > C:\folder > [color:#009900]true[/color]
Name is a directory > C:\folder\ > [color:#990000]false[/color]

That means the conditions tested with the string "C:\folder\" returns:
the name exists (correct) but it's no file (correct) nor directory (but it is!).
So it exists but is nothing of both. That makes no sense. Please fix this.

Here is another small issue in the Expression Calculator:

Retrieve a global value / string > Use a calculation will replace the whole text in the Expression Calculator.
That's unlike the other expressions will be inserted.

I found a few bugs/errors working in MMF recently -

When typing in a string it deactivates/greys the Workspace Toolbar etc for some reason. Im not sure why it does that but instead it should just go out of edit mode for the string and on to whatever you clicked instead.

In the event editor if you Ctrl+Drag then drop on to a new condition to copy if you are in a group it will not copy to inside the group but make it below the new condition slot to the next non group slot.

In the events editor if you use the save as command it will clear your undo/redo history. For me this is unwanted behaviour and it seems to not happen in the level editor which keep them. It should only clear them after closing MMF and loading that project again in my opinion.

Edit -

Also not sure if you have seen these but here is various simple ideas that would enhance the app/workflow a lot -

http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=151514#Post1515 14

Quote:

---

Originally Posted by Gustav

I found a small unhandy issue in the File object, maybe you want to fix it.


Say there is only a folder (no file) named C:\folder on our system:

Name exists > C:\folder > [color:#009900]true[/color]
Name exists > C:\folder\ > [color:#009900]true[/color]
Name is a file > C:\folder > [color:#009900]false[/color]
Name is a file > C:\folder\ > [color:#009900]false[/color]
Name is a directory > C:\folder > [color:#009900]true[/color]
Name is a directory > C:\folder\ > [color:#990000]false[/color]

That means the conditions tested with the string "C:\folder\" returns:
the name exists (correct) but it's no file (correct) nor directory (but it is!).
So it exists but is nothing of both. That makes no sense. Please fix this.

---

OK, we'll fix it, but you should not have a '\' at the end of your filenames if possible, Windows functions don't like it (as you can see with these conditions), so even if we fix it in these conditions there could be other issues in your application.

I noticed some Windows functions require the \ at the end, and other require it NOT to be there, and yet some allow for either. I always test before I really attemt to do anything that could mess up my game/application.

For the File object thing you could maybe add a extra condition maybe something like 'Name ends with \' that way you could just check although you could do this with string parsing also.

Right$( FilePath, 1 ) = "\"

Quote:

---

Originally Posted by Yves

Quote:

---

Originally Posted by Gustav

I found a small unhandy issue in the File object, maybe you want to fix it.


Say there is only a folder (no file) named C:\folder on our system:

Name exists > C:\folder > [color:#009900]true[/color]
Name exists > C:\folder\ > [color:#009900]true[/color]
Name is a file > C:\folder > [color:#009900]false[/color]
Name is a file > C:\folder\ > [color:#009900]false[/color]
Name is a directory > C:\folder > [color:#009900]true[/color]
Name is a directory > C:\folder\ > [color:#990000]false[/color]

That means the conditions tested with the string "C:\folder\" returns:
the name exists (correct) but it's no file (correct) nor directory (but it is!).
So it exists but is nothing of both. That makes no sense. Please fix this.

---

OK, we'll fix it, but you should not have a '\' at the end of your filenames if possible, Windows functions don't like it (as you can see with these conditions), so even if we fix it in these conditions there could be other issues in your application.

---

Thanks, you're right.

Maybe it's the better way to make the condition Name exists > C:\folder\ > false.
Because C:\folder\ isn't a valid folder(?).

But the first way I suggested would make our lives easier I think. ^^
It would be good if MMF were able to handle this. Like it does in other conditions.

I only wanted to say that all the conditions should work in the same way (need or allow "\" or not).



@LB
Yes, me too. It's very confusing all the time...