Active Picture and Layers Bug

[Stefan]

Hi,

I finished my work in MMF2 and wanted to build my iOS App on Mac, but there seems to an exporter problem when exporting active pictures on layers. I created a sample project to duplicate the problem. Basically, I have this scenario:

- 1 frame with 3 Layers.
- 1 Active picture for the background on layer 1
- 1 Active on layer 2 (Player)

When I export the project to iOS and run it on the emulator the active picture will not show up at all. Is this a known issue? I updated MMF2 to version 255, but nothing changed. Please advice.

[Jeff]

Did you upload the right file?
There are no objects on the frame or on any of the layers.

[Stefan]

Hi Jeff,
sorry, I didn't save the latest version. Please check the attached file.

[Jeff]

Can you try:

Remove the picture URL from the active picture property

On start of frame
Load under active picture
New picture
(click expression)
Put in "Himmel_Hintergrund.png"

Give that a shot and see what happens. I don't have my MAC hooked up at the moment to actually try it or to see how to include the picture along with my project.

I think if you hard code a path in the properties it won't translate over correctly in the runtimes.

[Stefan]

I tried what you suggested, but it the image is still hidden / not loaded correctly.

[Stefan]

No answer? I cannot publish/test my app on iPhone as long as this isue is not solved. Its clearly a bug in the exporter module. I need a fix or at least a workaround, please.

[arsdigita]

Did you add the external file to the resources in xcode?

[Francois]

No the iOS runtime only keesp the name and extension parts of a pathname.
Andos will have a look at it.

[Anders]

You should only keep the text "Himmel_Hintergrund.png" in the filename property box and include the active picture as a resource in your xcode project.
After quite a lot of feedback on the Active Picture we implemented the ability for it to support sub-folders in your project since many users had a whole lot of pictures they needed organized into folders.
Sadly we cannot easily do an automatic removal of the path component if it is entered in full in the property dialog as the runtime itself is not aware at which base folder it was located when built. I'll ask Yves if it is possible for him to automatically remove the path to the application from absolute paths at buildtime so it becomes a relative path instead.

[Stefan]

Thanks for your help. I'll try what you suggested and will give you feedback ASAP.