Does anyone know of any particular issues using hot spots on a grouped object? I'm able to add a hot spot to my group and see it, but it doesn't respond in preview mode, not even to just hovering over it. I've ensured it's the top most object.
Sounds like grouping it interferes with its normal function. Groups don't play nicely with lots of different functions. Some wild guesses:
1. Forget the hotspot and attach the triggers to the group.
2. Just put the hotspot on top of the group.
3. Forget the group. Many times the only use of a group is to keep the developer from screwing things up. If that's the case, work carefully and you may not need the group, nor its complications.
4. ATTACH the file here, and maybe someone can give you some help that is bound to be better than my wild guesses.
Seriously, groups seem to be a good idea for those of us who come from a MS Office past, but they are implemented differently in SL than Office. I find that they create more work, rather than less. It is easier to make a solid case for not using them, than for using them. Of course, your mileage may vary, but my advice is not to use groups, unless you MUST.
Thanks for your response! I'm pretty sure it has to do with the group as well - as you say, groups do not play nicely with many desirable features in my experience (though for me, coming from a CS background, they are key for consistency and efficient design).
I tried placing the hot spot on top of the group (rather than as part of it) and alas, that doesn't work. I do need this object to be grouped since all the elements move along a motion path in concert. In fact, that is why I don't want to ungroup them if at all possible. If I do, I lose the motion path and all the triggers associated with the group which leads to a lot of rebuilding.
I'm continuing to play around to see if I can come up with a less labor intensive solution.
3 Replies
Sounds like grouping it interferes with its normal function. Groups don't play nicely with lots of different functions. Some wild guesses:
1. Forget the hotspot and attach the triggers to the group.
2. Just put the hotspot on top of the group.
3. Forget the group. Many times the only use of a group is to keep the developer from screwing things up. If that's the case, work carefully and you may not need the group, nor its complications.
4. ATTACH the file here, and maybe someone can give you some help that is bound to be better than my wild guesses.
Seriously, groups seem to be a good idea for those of us who come from a MS Office past, but they are implemented differently in SL than Office. I find that they create more work, rather than less. It is easier to make a solid case for not using them, than for using them. Of course, your mileage may vary, but my advice is not to use groups, unless you MUST.
Hi Walt,
Thanks for your response! I'm pretty sure it has to do with the group as well - as you say, groups do not play nicely with many desirable features in my experience (though for me, coming from a CS background, they are key for consistency and efficient design).
I tried placing the hot spot on top of the group (rather than as part of it) and alas, that doesn't work. I do need this object to be grouped since all the elements move along a motion path in concert. In fact, that is why I don't want to ungroup them if at all possible. If I do, I lose the motion path and all the triggers associated with the group which leads to a lot of rebuilding.
I'm continuing to play around to see if I can come up with a less labor intensive solution.
Best,
Caryn
Can you ATTACH your .story file, or at least a representative slide?
This discussion is closed. You can start a new discussion or contact Articulate Support.