I'm so glad! This is an effect that people have asked about for a wide variety of activities, so after I made the video in response to your question we decided to add it to our user guide as well. So thank you! :)

Here's a link to a quick video of the process:
https://www.dropbox.com/s/7wsujk8jlle0ri9/Hat%20Intersection.mov

When you click the Intersection button, the yellow cross in the bottom left corner of Design mode, you'll see the window for setting up intersections.

For this effect, you'll be creating two different intersection behaviors. For both of them, Element 1 will be the hanging hat, and Element 2 will be the transparent element (or the character) with which the hat should intersect. The behavior should be to hide the hanging hat.

Then add another intersection by clicking the green plus sign in the intersection window. This intersection will have the same elements for Element 1 and Element 2. The behavior this time will be to show the hat that is placed on the character's head.

This means that when the hanging hat is moved over the character's hat, it should disappear and show the correctly-placed hat.

Does this work on your side? If not, I'll post a quick video.

At this point there aren't behaviors that can send information to email addresses, but some apps include a page that displays some information like the amount of points achieved throughout the different pages of the app.

You can share an unlimited number of times with each email address.

Here's an outline of this information, which we recently added to the user guide:
http://help.interactbuilder.com/s/5404/m/16264/l/196583-how-many-people-can-i-share-my-app-with

I've added a note to the user guide now so that it's more clear. Thank you!

If you'd like the text to be editable on each page where it is available, you can use the notes element like in the instructions here: Notes

If you want the text to simply be visible and not necessarily editable on each page where it is visible, then you can use the following steps. The text element will have the same location and appearance on each page:

1. On the page where the user can edit the text, add an element separate from the text that asks the user to enter the text (a button that they click in order to start editing). That element would have the following action sets:
- Interaction: Tap, Behavior: Text > SetText, Target: the text element that will be customized.
- Interaction: (none), Behavior: Text > SaveText, Target: the text element that will be customized.

2. Open the action set manager to chain the behaviors so that SaveText happens right after SetText.

3. Make the editable text global.

4. For any pages where you don't want the text to be visible, open the page options, and under Features change the Show Global Elements field to No.

Hi Jamie, thank you for pointing this out! Alin and I tried some tests, and it looks like the best option is to have the MenuClose button invisible on page load, but then for the two action sets that it uses, make both of those also execute on page load. That way, the button that opens the menu will always be visible when a new page opens, and the rest of the menu elements will be invisible. I've added this detail to the user guide. Thank you again!

When you're on the Manage screen and click the Reveal Default Folder option under the settings gears, does it accurately display the project group that contains the app folder?

If that looks correct, could you try compressing the app folder and sending it to inna@interactstudios.com? I'll check if it opens on a different computer and whether we can find out why it's not opening.

What type of file is it? Is it an image file that you are bringing in as a graphic element?