Forum Discussion
Trigger can't change state of a Group
I have a Group on one slide that is just a tiny graphic and a text box, grouped. I want to hide it using a Trigger.
I can't. Groups don't appear in the "Set state" trigger target menu.
Weirdly (to this former software designer) Groups do appear in the list of things you can click on. Just not the things you can affect with a Trigger.
Might I suggest that there is no reason to make us use two triggers (or more) to hide a Group by setting its state to "Hidden"?
(Have you considered adding a tag for "Usability" or "Suggested improvements" or some such thing to this discussion area?)
6 Replies
Separate from this Discuss Articulate Products section of the site, there is a Suggest Ideas one, though I'd agree it's not always intuitive. Or maybe the forum could use a way to cross-post more easily.
I'm also with you on setting the state of multiple grouped objects. I don't expect every groupable object has the same methods, and they certainly don't all have to have the same states, but they do all share some default states that you'd think would be easy to cascade an update to.
Thanks. I just want to set the Group to Hidden or Default. I'm tempted to just move it off the screen instead of hiding it. Motion paths are easy.
I prefer what I call "introverted programming." It avoids Groups.
Instead, I insert objects into another object while editing the states. That's especially useful when you want a graphic with a text box.
This post has more info:
TIP: Making icons easier to program and easier to click | E-Learning Heroes
Thank you.
Currently, you can hide Groups using JavaScript only by targeting the “select group” by its data-model-id and assigning the hidden class. Example below:
const group = document.querySelector('[data-model-id="6Sxwfs3MmIr"]'); group.classList.add('hidden');To unhide the group, remove the hidden class:
const group = document.querySelector('[data-model-id="6Sxwfs3MmIr"]'); group.classList.remove('hidden');This can be done with the Execute JavaScript trigger at any available event.
Thanks, but because the next person to work on the module I'm creating could be anyone, including someone not comfortable with JavaScript, I am avoiding it. I'll just use multiple triggers. Annoying, but it does work.
