Instance Communicator is broken

[MechatheSlag]

it just won't work at all

I have no idea what I'm doing wrong to be honest. Done exactly as the help files tell me to, yet they don't seem to work at all.

All help appriciated.

[MechatheSlag]

It's supposed to show more than one instance, which it does not. Please help

What it looks like to me (if that helps):

[Jeff]

When I build that into an EXE and run it twice it says 2 on both of them.

Did you expect the sub-app inside the main EXE to be a seperate instance? Its not just the main EXE is counted as an instance.

[MechatheSlag]

Oh. Very well, I didn't know that.

Does that mean I'm unable to send data through subapps using the Instance Communicator?

Because in the documentation it says

Insert a new 'Instance Communicator' object into one frame. Tick the 'Private' property to limit messages to between subapps. Copy the object and paste it into each subapp to ensure they all use the same settings (including GUID). Read the references on actions, conditions and expressions to learn about the types of message you can send - note that either 'send to first' or 'send to all' will work equally well in this situation.

[Jeff]

That should work and there are many ways to communicate data to a sub app .. It might just not be considered a seperate instance.

[Jeff]

I put the latest version in the released extension forum and it has the examples with it so you can check out the subapp data sharing example.

[MechatheSlag]

Ah, I forgot to toggle on "allow messages to yourself"
works perfectly now

thanks!

[MikeB]

I love the instance comm. object. I used it to pass data along to the other app. and limit how many can be open. Does the trick.