Including external files question

[Blizna]

I need to do something like custom installer. In MMF1.5 it was easy, I add all files in the Project and they were all in the EXE, unpacked somewhere when run. But in MMF2 it doesnt work for me. Im using Add binary, there I select the file. In the program Im using Copy "filename.ext" to "defined path". I guess the problem is "filename.exe" because its unpacked to different place.

[Blizna]

No advice?

I think its maybe the same "problem" as in MMF1.5 that the app is unpacked to some temporary folder and there was a way how to retrieve this directory. Or is there any other way could I work with files attached to the add? (using Binary data, Add in the Data elements.

[Yves]

Have you tried the "Include external files" option? If this option is selected, all the files that are defined in the object properties or in the events (in filename parameters, not in expressions) are included in the stand-alone application and unzipped when the application starts.

If you add files to the Binary Data tab, they won't be extracted to the temporary folder, the objects will usually access the data directly in the EXE file.

Yves.

[Blizna]

That doesnt work.

I want to do simple task: Copy one file to a location. Its screensaver. I want to have one EXE file. But If I add it as Binary, its not extracted so I cant copy it :/ And Include external files doesnt work too because I cant specify the file other way than in event editor.

Im missing there a simple feature Add external file <img src="/center/images/graemlins/frown.gif" alt="" />

[Yves]

This option is on the wish list, we'll do it later probably.

Solution: create a fake frame, add an Array object, open the event editor, add an event "Never / Load array from file xxxx.xxx" (select the file from the file selector, not via an expression), build your application and run the EXE file, the file xxxx.xxx will be extracted to the temporary directory, you can copy it from there (AppTempPath$ + "xxxx.xxx").

Yves.

[Blizna]

Thank you! Im glad there is this workaround.

[workshop2]

Is the extracting on binary files going to be in the next update at all?