Grouping with hidden elements issue/query

James shared this question 5 years ago
Answered

Unsure whether this is a problem or implemented on purpose, but when grouping elements whereby one of the elements may be hidden, the elements behind the hidden element cannot be accessed.


The solution to my problem was to ungroup the two items. This meant that the elements behind the hidden element could be accessed again. This is causing a problem for me as I wanted to use this as a master for my prototype where the two elements are used frequently across all pages and making the change to the item would mean changing every page.


Any replies would be greatly appreciated.

Comments (4)

photo
1

By 'accessed' you mean that you can't select them in Prototyper or that the events defined in those elements don't work in simulation?

photo
1

When in simulation elements under the hidden element in the group cannot be accessed.


For example, if I had a drop-down menu that appeared when a button was clicked. This drop-down menu would then appear over data within a table. When I have the button and the drop-down menu grouped, the data within the table where the drop-down menu covers cannot be selected even if the menu is hidden. If I ungroup these element it solves this problem but I'm not happy with this solution as it means when I copy across this group to all pages I have to un-group them all. As stated above, if I wanted to make a change to all pages, I would have to copy/paste to all defeating the purpose of a master.

0ffccf367597e1f32f2744ec4781d791

photo
1

I'm afraid that's how it works right now. The group act as a 'container' so even if some of its components are hidden, the 'container box' is still visible. I know it doesn't have any sense, if fact we're already fixing that for the next release (that we plan to launch in a month or so). Sorry for that.

photo
1

Fixed in version 5.5