Message Event Documentation Feedback

#1

tl;dr: I don’t think the documentation of Message Events does enough justice to help explain what the feature is for or how to use it.

I’ve been trying to understand the use cases behind as well as gain a general understanding of the fundamentals of Message Events, but the documentation on site doesn’t really help too much (But maybe it’s just me.) I’ve tried messing with it myself a few times but I’m still having trouble grasping the way it works.

  1. This video/gif highlighting the way to use it ends pretty abruptly and shows the ability to control which artboard you’re navigating to (from my understanding)
    https://principleformac.com/static/video/toparent.mp4

  2. While text documentation is helpful, additional imagery or video would go a long way to explain the general use case and functionality.

I believe there’s a bidirectional communication that is required in order for this to work properly, but I can’t seem to figure out how to do that, or what that means.

My initial thought based on the documentation was that this would allow me to maintain a state-based object (e.g. a button with a hover state) to control where you might be within another artboard.

I was assuming I could create a cancel button (component) to dismiss a modal (artboard) for example. But perhaps I’m totally misinterpreting what the use case is.

1 Like

#2

I agree with you, tried reading the documentation to understand how the messages between components work, but the explanation is not very clear and the video doesn’t show the actual use, more work would need to be done, but I believe Daniel is working on some new tutorial that I hope throw some light on this.

Your best chance is to try use them yourself and learn from it.

2 Likes