Help Building Decision Tree Tool in Storyline
Dec 23, 2018
Hi,
I've started building a copyright advisor resource in Storyline and stumbled across a problem that's resulting in me being unable to preview the project - I just get a spinning wheel. I wondered if the Articulate community may be able to help me establish where I've gone wrong and get my project back on track?
The project is essentially a decision tree app that requires the user to first select the resource they have [image, video, audio, book, journal or code] then they're asked a series of questions that will help them to decide whether their use of the resource is likely to infringe on copyright or not.
I'm attributing True/False variables to the resource buttons that allow me to use triggers to show the relevant content based upon the users' choices. E.g. Set btn_image to True and Go to Slide 2 if user clicks btn_image.
I only have 4 slides so far, but there's already quite a lot of triggers in the project and struggling to see where I've gone wrong. If anyone is kind enough to look at the attached project, I'd appreciate any advice on where the error may lie.
Thanks in advance :)
11 Replies
Hm, this works for me. I can preview and publish, see a quick test here.
Hi,
You never mentioned what is the problem? What do you want to happen?
Hi, sorry the problem - for me at least is that when I try to navigate from one of the homepage buttons e.g. 'Image', I just get s spinning wheel and the resource doesn't navigate to the 2nd page as it should.
I wonder if I've just hit a bug of glitch in my version of Storyline. Pleased to hear it works for you. I was concerned I'd just made some fundamental error.
As you can see, you have Group objects as shown below.
The trigger is added on the "img_btn" object. So when you try to click on the "icon" and "Text Box" objects, it will not work.
I suggest to create a Button and put all of these objects into it.
Ok thanks Daniel, I'll give that a try. Hopefully that'll improve things.
Ok I have rebuilt the buttons in this project, but I still get the spinning wheel upon pressing any button on the home page. I've even tried simplifying it by removing all but two slides in the hope of identifying a bug later in the project, but that hasn't worked either.
For the sake of testing, I created a new blank slide and tried adjusting the image button to go to that slide upon click - and it worked! So I'm wondering if there's something in the slide 1.2 create_write that's causing the problem?
To clarify:
1. I have 6 buttons on the homepage, with 6 corresponding variables that are set to False by default.
2. Upon clicking a button, the corresponding variable is set to True and the user is taken to slide 2 e.g. Upon clicking btn_img set var_btn_img to True and go to Slide 2.
3. On slide two there are two layers; one that contains the word create, the other that reads write. If the user selects image, video or audio as the resource, they will see the 'create' layer. If they select book, journal or code they'll be taken to the 'write' layer.
This is just the start of the project, but I'm already encountering an error where I get a spinning wheel in preview or when the project is published.
Here's the published version. I've also attached the project file.
Any ideas where I'm going wrong?
Thanks
Hi,
I don't see the Spinning Wheen on Preview but I see on your Published version.
The triggers on the layer may not be needed.
I will try to create a different method but the same result.
Edit: See my attached version with a lesser trigger.
Hi Daniel,
I just tried this and it works!!! Thank you. I'll continue using this, but I'm not familiar with the if SET equal to 1 method. By 1 is that essentially a boolean that is True?
Thanks,
Ross
Hi,
The SET Variable is for Write and Create.
I called it SET because there are 3 buttons for Write and 3 for Create.
The idea is when you click the IMAGE, VIDEO, AUDIO, SET is equal to 1.
And when you click BOOK, JOURNAL, CODE, SET is equal to 2.
The SET variable is not a boolean.
Ok I see, thanks for clarifying.
This discussion is closed. You can start a new discussion or contact Articulate Support.