Skip to main content
Ben Posch has been posh
Participant
August 13, 2021
Answered

Can't define Component Hotspot?!

  • August 13, 2021
  • 1 reply
  • 831 views

i have 5 components. each has a default state where you can only see a button, and another state where you can see a transparent image in the area beneath the buttons. in prototyping this project, the user should be able to toggle on and off the images at will by clicking 1 of the 5 buttons, and the layers remain in the same order (5 is always the bottom layer, 1 is always the top layer) no matter which order you turn them on and off.

problem is, an xd component hotspot area is not definable, it's just the shape of the whole component by default. which means the top layer is always triggered, even when there is no content in that area of the component. this would be an easy fix to create an interaction mask that makes only a certain area of a component interactive.

i jerryrigged it by getting rid of the buttons and using the keys & gamepad trigger to avoid this, but functionally it's a very different user experience. is there another way to handle it?

https://xd.adobe.com/view/2f6974bc-fa61-410d-9150-37571e371e05-7a3a/

This topic has been closed for replies.
Correct answer Spas K.

Hi there, can you check if this is what you need? Made a quick example and it seems to be working with toggle states. Components are overlapping slightly with neighbour buttons, but it doesn't seem to be an issue. Here's the file as well.

1 reply

Randy Edmunds 2
Adobe Employee
Adobe Employee
August 14, 2021

I think you can achieve this by defining Transition on a sub-node of the Component (not the Component itself), with Destination of the other State. 

 

Hope this helps,

Randy

 

Ben Posch has been posh
Participant
September 7, 2021

i can't figure that out. everytime i try, i have the same result, that the active state of any component covers the entire area and can only be turned off before another is activated.

Spas K.
Community Expert
Spas K.Community ExpertCorrect answer
Community Expert
September 7, 2021

Hi there, can you check if this is what you need? Made a quick example and it seems to be working with toggle states. Components are overlapping slightly with neighbour buttons, but it doesn't seem to be an issue. Here's the file as well.