I've seen discussions of creating custom buttons for the Feedback Master in Storyline 1. It involved a process that included moving the default button offstage and adding triggers to the custom button.
I've not been able to get this to work, so far, in Storyline 2. If I create a custom image to act as my button, on the Feedback Master, with states and triggers, it isn't functional or clickable on the resultant Feedback Layer. Am I missing something, or is there something different about Storyline 2?
I may not be following your question - but if you include an element on a master, it won't be clickable while on the layer editing it for the purposes of adding triggers and such. It should work as you set up when you're previewing the course or viewing the published output.
If I'm misunderstanding or you're still having difficulty could you share the .story file with the custom feedback masters you set up?
If you've included a custom button on the feedback master, you have to set the triggers on the master so I'd use generic ones such as "jump to next slide" as you won't be able to say on the individual slide layers jump to slide # X when the user clicks. But if you add triggers on the feedback master themselves, those should work as normal.
The options you mention would work as well - with Storyline you can do most anything in a few different ways.
If you have a file where you've set something up that isn't working as described or expected, please feel free to share here so that we can take a look.
And further testing reveals what you have suggested. Putting an image on the Feedback Master, and using generic triggers such as Hide This Layer and Jump to Next Slide are now working.
I can't explain why I couldn't get an image, with Hover and Down states, to work properly, earlier. But now it is. Clearly user error.
But I want to confirm: On the Feedback Masters, is it necessary to keep the standard button and move it off stage? Or can that button be deleted off the Feedback Masters?
I encountered the same issues with my feedback masters.
Here is what I want to do:
create a master for my layers (regular layers, not in a quiz) and add a button to close that layer,
so that users click from the base layer, open a layer and are able to hide it using a button that would be in the feedback master (not providing feedback at all, but this is the only master we can apply to our layers)
It's all working well BUT the trigger in the feedback aster "hide this layer" doesn't work. In conclusion: do we have to add this trigger in every layer manually? There is no way to have this behaviour in a master?
The layers will default to using feedback masters as their layout options and you can read more about the feedback masters here. As for the button and associated trigger that you've set up - are you able to share a copy of your file so that we can take a look at it?
Thank you for your reply. What I understand is that the "hide this layer" trigger doesn't work when it's in a feedback master layout (and it should be disabled so that we are not mistaken!).
Here is my file. I removed everything else. So if you click TAB 1, you have this layer with a yellow cross button, it is part of the feedback master layout. It doesn't hide the layer when clicked.
Thanks for sharing the file - I thought I understood you correctly but wanted to take a double check by looking at it. Yes, the trigger will need to be on the actual layer, as that's the layer you're trying to close - whereas referring to the feedback master (and a layer within that) won't close that particular layer. You'll see the same thing if you were to take a look at a standard question slide - the hide layer and jump to next slide layers are on the question's layers vs. being a part of the master. Sorry for the confusion there in that you can still access the triggers - but we don't currently have the set up to have certain triggers disabled based on what you can and cannot do.
You could use the format painter to copy from slide to slide - or once you create the button and add the triggers you could also copy the button to the new slides which is a few less steps than recreating it from scratch each time.
I just wanted to pop in and say I agree with Helene I am trying to do something similar in a training program. I have review layers after the question is answered incorrectly to many times and would lover the ability when the student is done reading they can just close that layer and go back to the base layer to retry the questions. Having the ability to use "hide layer" trigger only on the master feedback layers would be fantastic! I hope there is a way to include that in future versions.
Thanks Melissa for sharing your thoughts and particular use case here - it's always good insight to have! I don't have any intel into this as a new feature yet. I also wanted to share a link to our feature request form here as that's another good way to share your thoughts with us and ensure those get tagged, tracked and into the hands of our product development team.
Has anybody found a usable workaround for this? I'm battling it now and it seems like all I find are threads going back 5 or 6 years with no resolution.
Since this thread is older, let's start fresh. First, what version of Storyline are you using? What exactly are you trying to do on your Feedback Masters?
19 Replies
Hi Gregg!
Would you be able to share the .story file that you are working on so that we could take a look?
Hi Gregg,
I may not be following your question - but if you include an element on a master, it won't be clickable while on the layer editing it for the purposes of adding triggers and such. It should work as you set up when you're previewing the course or viewing the published output.
If I'm misunderstanding or you're still having difficulty could you share the .story file with the custom feedback masters you set up?
In looking again at the discussions on using custom buttons on feedback layers, I realize that my choices appear to be:
For some reason I thought I could put a custom feedback button directly on the Feedback Master, but I'm now under the impression that I cannot.
Hi Gregg,
If you've included a custom button on the feedback master, you have to set the triggers on the master so I'd use generic ones such as "jump to next slide" as you won't be able to say on the individual slide layers jump to slide # X when the user clicks. But if you add triggers on the feedback master themselves, those should work as normal.
The options you mention would work as well - with Storyline you can do most anything in a few different ways.
If you have a file where you've set something up that isn't working as described or expected, please feel free to share here so that we can take a look.
The crux is that I'm trying to use an image as a button.
And further testing reveals what you have suggested. Putting an image on the Feedback Master, and using generic triggers such as Hide This Layer and Jump to Next Slide are now working.
I can't explain why I couldn't get an image, with Hover and Down states, to work properly, earlier. But now it is. Clearly user error.
But I want to confirm: On the Feedback Masters, is it necessary to keep the standard button and move it off stage? Or can that button be deleted off the Feedback Masters?
Hi Gregg,
In Storyline 2 you can safely delete it. I tend to keep it just moved off the slide just in case though. :-)
Hi all
I encountered the same issues with my feedback masters.
Here is what I want to do:
It's all working well BUT the trigger in the feedback aster "hide this layer" doesn't work. In conclusion: do we have to add this trigger in every layer manually? There is no way to have this behaviour in a master?
Hi Helene,
The layers will default to using feedback masters as their layout options and you can read more about the feedback masters here. As for the button and associated trigger that you've set up - are you able to share a copy of your file so that we can take a look at it?
Hi Ashley,
Thank you for your reply. What I understand is that the "hide this layer" trigger doesn't work when it's in a feedback master layout (and it should be disabled so that we are not mistaken!).
Here is my file. I removed everything else. So if you click TAB 1, you have this layer with a yellow cross button, it is part of the feedback master layout. It doesn't hide the layer when clicked.
Hi Helene,
Thanks for sharing the file - I thought I understood you correctly but wanted to take a double check by looking at it. Yes, the trigger will need to be on the actual layer, as that's the layer you're trying to close - whereas referring to the feedback master (and a layer within that) won't close that particular layer. You'll see the same thing if you were to take a look at a standard question slide - the hide layer and jump to next slide layers are on the question's layers vs. being a part of the master. Sorry for the confusion there in that you can still access the triggers - but we don't currently have the set up to have certain triggers disabled based on what you can and cannot do.
Hi Ashley. Thanks. Too bad I will have to copy paste all the buttons in each layer... I hope this is something that will be doable in the future.
Hi Helena,
You could use the format painter to copy from slide to slide - or once you create the button and add the triggers you could also copy the button to the new slides which is a few less steps than recreating it from scratch each time.
Of course I do that, but it still is very amateur... I am creating templates for people to use, and I wanted to make their job as easy as possible.
Certainly understand Helene and will keep you posted if there are any changes to this set up.
hi guys,
I just wanted to pop in and say I agree with Helene I am trying to do something similar in a training program. I have review layers after the question is answered incorrectly to many times and would lover the ability when the student is done reading they can just close that layer and go back to the base layer to retry the questions. Having the ability to use "hide layer" trigger only on the master feedback layers would be fantastic! I hope there is a way to include that in future versions.
Thanks Melissa for sharing your thoughts and particular use case here - it's always good insight to have! I don't have any intel into this as a new feature yet. I also wanted to share a link to our feature request form here as that's another good way to share your thoughts with us and ensure those get tagged, tracked and into the hands of our product development team.
Has anybody found a usable workaround for this? I'm battling it now and it seems like all I find are threads going back 5 or 6 years with no resolution.
Hi Steve,
Since this thread is older, let's start fresh. First, what version of Storyline are you using? What exactly are you trying to do on your Feedback Masters?
This discussion is closed. You can start a new discussion or contact Articulate Support.