It’s rather “simple” how it works…
Flow when triggering a behavior
- Any custom behavior is sent to the local context as is!
- It is also sent to Global Behavior on the page level
- Global Behavior forwards the behavior adding a # infront to all Hype Widgets, even the one sending it in the first place.
Flow when triggering a targeted behavior
- Using the @ symbol directs the custom behavior to only the specified Hype widgets
- Hint: As in this flow the ping@C is sent to Hype GlobalBehavior and processed there. A internally actually only receives the string as is “ping@C” (little grey arrow)