Hello everyone,
I am trying to build a color wheel with multiple buttons in a spider’s web kind of layout. I imported an svg file and converted them into shapes and applied a Mouse Down interaction style for all shapes. The problem I am having is that each shape has a rectangular bounding box (see screenshot) so the buttons cover one another.
Is there any possibility to restrict the clickable area to the shape area only? I tried an approach with hotspots at angles but they too have the rectangular bounding boxes. Any ideas or pointers how to achieve having all buttons clickable would be greatly appreciated.
This isn’t a perfect fix, but changing the ordering within your groups will help a little bit. I put the biggest (outermost) shape as the last in the group and that improves things a little bit - look at gp01 and gp12 in the attached. I think the overlapping areas are better this way than the current ordering.
I used rotated hotspots to cover the overlaps and then set selected on mousedown to cover the gaps in gp12. If this works you could copy the group and rotate to match what you have currently.
Perhaps some smart people out there have a more elegant solution - but this I think would get the job done for you with a few copy/paste/rotate repetitions.
color_wheel_overlapping_areas.rp (82.8 KB)
Thank you UXProtoTyper, you’re right, the layer order improves this. I was hoping there would be a solution without using hotspots since for this color circle that would yield to 48 extra widgets just to make each button selectable.
Having shapes be clickable only in the area of the geometry would be definitley something on my feature wishlist.
Yeah, far from an ideal workaround, although I’ve done worse 
I completely agree with you on the shapes and the clickable area. I think the prototype ends up creating images from the shapes, and that is the culprit for the bounding boxes.
The custom shapes like this are a relatively new feature to Axure. You may want to post something in the feature request section to bubble it up to the Product Team’s attention. I’m not sure they’ll be able to fix it, but it doesn’t hurt to ask!
Yes, I posted it in the feature request section. Let’s wait and see, hopefully this will get fixed in a future update. Thanks, again