Okay, this isn't even a Scrolling Pane issue, it seems to be across the board - Can't access Grouped Objects in the Trigger Wizard, which I could have sworn I was able to do? Hmm...
Phil, to me that's just "grouping" too. Doesn't solve this issue, as I feel states serve a different purpose. Based on the following picture, this is either a bug or was lower on the "product backlog" during build - hopefully comes with an update.
Also, Scrolling Pane's don't register at all in the Trigger Wizard. HULK SMASH!
I can remember it ever working. I dont think grouped objects can have a state. I just started grouping this way because it worked.
It would be great if it did work, but I have this fuzzy memory of it never working, hence my work around. I even have a fuzzier memory that I may have bug reported this.
I probably dreamt about it working. Tend to dream about Storyline solutions.
Either way, I hope this gets fixed - Or Articulate recommends the "States Solution" for this. In my case, I'm always thinking about how this will work when output to HTML5... hate to spend a few hours thinking you have a solution, then having it break in HTML5.
It's still early, so much is still experiment at this point.
6 Replies
Okay, this isn't even a Scrolling Pane issue, it seems to be across the board - Can't access Grouped Objects in the Trigger Wizard, which I could have sworn I was able to do? Hmm...
I always grouped objects within the state (edit state then cut and paste) dont think you could do this
Phil, to me that's just "grouping" too. Doesn't solve this issue, as I feel states serve a different purpose. Based on the following picture, this is either a bug or was lower on the "product backlog" during build - hopefully comes with an update.
Also, Scrolling Pane's don't register at all in the Trigger Wizard. HULK SMASH!
I can remember it ever working. I dont think grouped objects can have a state. I just started grouping this way because it worked.
It would be great if it did work, but I have this fuzzy memory of it never working, hence my work around. I even have a fuzzier memory that I may have bug reported this.
I probably dreamt about it working. Tend to dream about Storyline solutions.
Either way, I hope this gets fixed - Or Articulate recommends the "States Solution" for this. In my case, I'm always thinking about how this will work when output to HTML5... hate to spend a few hours thinking you have a solution, then having it break in HTML5.
It's still early, so much is still experiment at this point.
Hi Ryan,
Groups don't have states. Thus, there's nothing you can change their state to.
This discussion is closed. You can start a new discussion or contact Articulate Support.