I have a text box, I want to change the text when hovered, so I did this.
That’s pretty simple. However, I found out you can’t hover on a phone, or even click. The only option is Press, which isn’t click.
So I added a 2nd text box behind the first with the changed text. Then I made a condition for first text to become invisible when pressed, and to remain invisible I added “or this text isn’t visible” with the property to make the element invisible. Since the first box is invisible, it allows the Back box to be pressed, and makes the 1st box visible again. Voila!
It actually works fine, but the page gives a “recursion error” warning on the condition “make this text invisible when it’s invisible. So I don’t know if recursion is a reason to fix it or not.
At any rate, I don’t have a different idea. Do you?
Thanks! 
Your first condition on the seconds image doesn’t make any sense.
What is it supposed to do?
True. Mobile has no hover because there is no cursor 
I had played around with something similar to this in an app. I scrapped the idea and went with something different…
what I did was just use a regular button and made it look like text. Took out padding, background color, etc.
Then a condition on desktop that when it was hovered, the text was xxxxxxx.
I had a custom state: ‘is toggled’, yes/no.
On mobile, when the button (text) was clicked i just set the custom state to yes and changed the text with a condition
When “text is pressed” makes the element invisible–but it does not remain invisible when no longer pressed.
Once it’s invisible the “or when text isn’t visible”–this triggers it to stay invisible. I don’t know if it makes sense or not, but it actually works. Although with recursion error.
That seems simple, I’ll try it!
1 Like
Yes, it works great.
Plus, it’s a breeze to set up
Even easier, I learned the “click” workflow action works when pressed on a phone, so I just made workflows to hide and show the text element.
Thanks Seneca.
1 Like
