Digital Workshop

Hi
I'm voluntarily creating an orientation publication for a volunteer wildlife rescue and rehabilitation organisation.
I have a text box dropping into a page.
On the left are some buttons that show smaller text boxes in response to mousovers.
Everything works as intended provided the user's mouse is not hovering over one of the mouse over buttons when the page shows.
If the mouse cursor is over one of the buttons, the dropping text box hides and the mouseover button show textbox appears and there doesn't seem to be any way to delay the hide.
I've tried to disable the mouseover by disabling the buttons for say five seconds, but it doesn't work if the mouse cursor is over one of the buttons when the page loads. It works if the cursor is not over one of the buttons but not the other way around.
One option is to create a page without functionality that appears for say 10 seconds to give the reader a chance to read the instructions and then to show an identical page with functionality.
But is there another way?
Have tried the pre-show action with no luck.
It seems that a mouseover has precedence and cannot be delayed
Thanks
Graham

It's all good!
Works OK in published mode
Doesn't work in preview mode
Should have tried publishing before posting on this board!
Thanks
Graham

Hey Graham, it's good you have a self-healing Pub. Professor Graham's motto: "Publish or perish!".

Even though you've resolved the problem, maybe I can suggest something of a workaround in case someone else encounters a similar hurdle.

I think you could create an IF test-condition, and place your mouse-over action under that.
For example on a Timeline, or on Page-show, with a few seconds Delay set some Variable to true. ( In your example, if the User is already hovering over the button, he would have to move and re-trigger the mouseover.)
An alternative IF-test could be to Show a hidden object after a few seconds, and using a simple expression such as object1.isShowing() in that IF-test --- would accomplish the same thing.

Cheers.

Thanks Lar!

That is so true - didn't think of an if variable solution. That would work well also.

Now, for some reason some of the text in text boxes has changed to outline for some unknown reason and I can't change the darned text back the way it was because the Opus text attribute buttons are not responding. Arrgh!!

Might not be Opus's fault - have other things running in the background.

Time for a reboot methinks.

Failing that, a reinstall

This week started so well ...............

Cheers

Graham

Selecting the initially disabled option for the object on the general tab should stop the mouse over event.

Mack

Hi Mac

I saw that but was unable to find anything in the help file.

I suppose if you checked the initially disabled box you would then have a frame that has an enable action to turn the disabling off.

What I did was have a frame with a pre-show trigger, then a disable object, a five second delay then enable object action in the publication.

There wasn't any problem after publishing. The problem occurred when previewing.

Time to experiment with the initially disable option and see if that works in preview.

Thanks

Graham
PS - Reboot fixed the font display issue which probably was a laptop display problem and not an Opus problem.

Didn't quite follow your original post. Normally, I just disabled and then add a delay and enable. User has to move mouse off and then back on - from memory.

Mack