Forum Discussion

DainJack's avatar
DainJack
Community Member
6 days ago

Creating an Interactive Texas Roadhouse Menu Simulation in Storyline – Having Issues With Triggers

Hi everyone, I’m working on a practice e-learning project where I’m trying to recreate an interactive Texas Roadhouse restaurant menu in Storyline. The idea is to let learners click on different menu items (like steaks, ribs, and sides) to reveal more details, almost like an ordering simulation. I’ve set up layers for each item, but I’m having trouble getting the triggers to work consistently when users click multiple times.

The main issue I’m facing is that some menu items don’t always return to their initial state after being viewed. For example, if a learner clicks on “Steak,” the layer shows correctly the first time, but if they return and click again, nothing happens. I’ve double-checked the trigger settings (“show layer when object is clicked”), but it feels like the states aren’t resetting properly.

I also tried adding variables to track whether an item has been viewed, but that made the logic more confusing, and sometimes layers overlap instead of hiding. What I’d really like is a clean way to let users freely click around the menu, view different food details, and always return to the default state without glitches.

Another challenge is making it mobile-friendly. Since many restaurants (like Texas Roadhouse) now use digital menus via QR codes just like this site thetexasroadhousemenu.com, I want this interaction to feel smooth on touch screens too. However, when testing in the responsive player, the text sometimes overlaps or buttons get too small to tap easily.

Has anyone else built a similar “menu simulation” in Storyline? I’d love advice on the best way to handle trigger resets and layer management, and whether there are design tricks to keep it mobile-friendly. Any suggestions would be a huge help—thanks in advance!

2 Replies

  • I'd suggest sharing your file so that someone can take a closer look and see if there's anything obvious going on that's causing the issues.

  • A slide has Slide Properties that include a setting for what should happen when the user revisits the slide: Automatically decide, Reset to initial state, or Resume saved state.

    Each layer has Slide Layer Properties that also include those "When revisiting" options:

     

    The "When revisiting" option for a layer can be different than the option for the slide/base.  

    Based on your description, it sounds like you need to change the setting for the layers to "Reset to initial state." 

    If that doesn't solve the issue, well, troubleshooting is just guessing without seeing all the programming. Someone might be able to solve the issue if you upload the .story file. Here are the best practices for doing that:

    • Only include slides that are related to the problem.
    • Be sure objects, layers, motion paths, and variables have meaningful names.
    • If there is proprietary content, replace or delete it. For example, replace proprietary text with “ipsum lorem” text.

     

     

    Storyline is not fully responsive. That means some content might become illegible, and buttons might be difficult to click/tap. You'd have to design slides accordingly. See https://www.articulatesupport.com/article/Articulate-360-FAQs-Responsive-Player?_ga=2.28850812.1918668082.1526936372-1731444521.1461185748 

     

    By the way, this question asks how to do something in Storyline. For future reference, it's better to post this sort of question in the Discuss Articulate Products section of the community. The Exchange Best Practices section is for general questions about eLearning.