I just wanted to make you aware of a bug I discovered.
If you group two objects together, of which one has a down state action, then clicking the other object trigggers the down state action of the first object.
I have put together an example that shows the problem.
If they are a group, isn't acting together part of the characteristics we expect of a group?
But this is just the tip of the iceberg. If you keep exploring, you will find that SL doesn't play nicely with groups in lots of ways. So many ways in fact, that I avoid groups entirely.
And no, I wouldn't expect different objects in the same group to trigger each other's actions. E.g. if I grouped three buttons together to form a dashboard than can be moved on/off the screen, I wouldn't expect that pushing button A would trigger the actions of button B or C.
if you group something in storyline you "merge" them together. So they act/behave like one object. This way you could even usa a group as a drag object. Thats why it´s storyline "logic" that a group has no seperate objects anymore which seems logical to me or I wouldn´t need a group.
See this article which says "Grouping is a handy way to move, size, rotate, flip, or change other attributes of multiple objects at the same time—as if they were a single object."
But a group does indeed have separate objects which you can change state of, trigger actions with and all the other stuf, which works well except for the down state issue.
In my case, I need the group function to move a dashboard containing lots of buttons and input fields on/off screen as needed, rather than creating a motion path for every single object.
5 Replies
If they are a group, isn't acting together part of the characteristics we expect of a group?
But this is just the tip of the iceberg. If you keep exploring, you will find that SL doesn't play nicely with groups in lots of ways. So many ways in fact, that I avoid groups entirely.
Hi Walt
Thanks for your answer.
And no, I wouldn't expect different objects in the same group to trigger each other's actions. E.g. if I grouped three buttons together to form a dashboard than can be moved on/off the screen, I wouldn't expect that pushing button A would trigger the actions of button B or C.
Hi Martin,
if you group something in storyline you "merge" them together. So they act/behave like one object. This way you could even usa a group as a drag object. Thats why it´s storyline "logic" that a group has no seperate objects anymore which seems logical to me or I wouldn´t need a group.
See this article which says "Grouping is a handy way to move, size, rotate, flip, or change other attributes of multiple objects at the same time—as if they were a single object."
Susi
Hi Susi
Thanks for your answer.
But a group does indeed have separate objects which you can change state of, trigger actions with and all the other stuf, which works well except for the down state issue.
In my case, I need the group function to move a dashboard containing lots of buttons and input fields on/off screen as needed, rather than creating a motion path for every single object.
Hey Martin,
Susi B. is absolutly right. But you can inherit the motion path to all Objects. See the attached example.
bw
Philipp
This discussion is closed. You can start a new discussion or contact Articulate Support.