Click Behind Text Box (Text Box Above Clickable Object)

Hi Simon,

Thanks for reaching out here - I think we'd want to take a look at the .story file and how you've set up the clickable object and text box properties. Also where are you testing this course? You'll want to make sure you're testing the published output in the intended environment as detailed here. 

Hi Ashley,

Thanks for getting back to me - you can find my story file at this link:

https://community.articulate.com/discussions/articulate-storyline/multiple-countdown-timers-link-to-triggers

The text boxes in question are the "OFF/ON" components of my three switches.  Currently the entire switch image is clickable, however not the areas where the text boxes sit.

Hope that makes sense?

Hi Simon,

Thanks for linking to that thread where your course is. I took a look and didn't see anything off in the way the text boxes are set up, and that should work (I confirmed on a new file with just a text box over an object). I'd want to confirm that you were working on local project files as well as described here.  I tried stripping it down to just a few of the triggers on one of the buttons and one text box, and it seems once you remove the state associated with the text box, then you are able to click on the element. It seems the additional state is interfering with that - have you looked at creating each of the states of the button as one entire image vs. changing the state for 3 elements at each click? 

Hi Ashley,

Thanks very much for your in depth work - understanding my project and coming up with that suggestion would have been time consuming for sure.  I tried to replicate my problem with a new project and discovered the same as you (I concur; it's the text box states that are not allowing a "click through".

I'd considered merging the "ON/OFF" elements into the actual image, which would also cut down on the number of triggers - that probably would have been wiser, and also fixes the problem.

I found an acceptable solution by reducing the margins on the textbox to zero.

Its still a work in progress, but please see attached project.

Glad I was able to assist Simon and help narrow that down. It was a tricky one with all the triggers for sure. :-) 

Glad you found another solution that worked for you as well!