Digital Workshop

Using Opus Pro 05

Tool Tips are mentioned in the Help files as a common action for a MouseOver.

BUT, I can't find info on how to do them in the help file or the forum.

Am I missing a tutorial on this?

Thank you,

When you make a Tool Tip, there are actually two OPUS Objects involved.

First, create a Text Object, then add some "Tip" which you want to appear when you roll over a specific area. Go to Properties and tick "Initially Hidden."

Now create a Frame Object, placing it over whatever you want for your Tool Tip. If you want it over a Button Object, or a single Image or Text Object, then you can skip the Frame, and go to the next last step.

Finally, double right click the Frame (or other Object) and select a Trigger of "Mouse Over." Next select an Action of "Show." Pick the hidden Text Object with your Tip to show.

When you Preview, you'll see that when you mouse over the desired Object, the Tip appears.

OK, go back and add a second Trigger of "Mouse Exit" with an Action of Hide, then select the Tip Text Object. This will make the Tip disappear when you move your mouse off.

Thank you. I will let you know how I do. If this works for me, I highly recommend that it gets posted some where. I imagine it's a very implementation.

You could have a look at the tool tip template available at the following link:

http://graphicsinaction.com/forum.htm

The Basics gallery supplied with Opus has a simple example tooltip button. You can extend or change that as you need then save it in a gallery for reuse.

Thanks everyone--I was very hopeful. Seemed easy when reading it.

Nada. My background is web design via code (so not an expert at WYSIWYG modes) and print graphics, etc. My guess is that I am missing something that is "no duh" to you all!


When i used the tooltip in Basic the mouseOver area was so large as to be distracting and I couldn't get that box smaller (I tried, but then it would eithr refuse to shrink or revert to orginal size).

I downloaded the template from
http://graphicsinaction.com/forum.htm. Worked in the template but couldn't get it to copy correctly into my doc.

I lastly tried the text box behind my button but it showed forever in the pub. Seemed similar to javaScript so i went into Actions and tried to add a Hide function. Voila! The tip disappeared altogether!

My idea now is to try to build my pub around the template page from http://graphicsinaction.com/forum.htm.

Thanks for you help.
~margaret

You might have seen a few of my contributions tending to favor scripting in publication development.

Here is my take on a scripting way to implement this.

Depending on number of objects on any given page that requires a tooltip, having to create a text window for each would mean the development cycle will be overburdened by too much objects needed to be placed on the canvas, moved to desired location and have code association for each. For me that is too much work.

In script, I would have the "ToolTip" listed in a dataset, either in file or defined on the publication as an array that has some tying reference i.e

button1:Help is at hand
button2:Need a consultant for this
button3:I needed the help as well

above dataset separated by ":"


In my publication, I will decide, on mouseover, where I want the tip to appear, Would standardise this to the right hand corner of the object for which I need the tip, via script, I would pick up say the x,y position of the object so that I can use it with the text object... so, With only one text object for the whole page, would "move" it to the location of the calling object, change/set its text and that's it.
The mouseover actions above would be as follows

0). See if this object has a tooltip by querying the dataset
1). if 0). is true, get x,y 'position' of this object
2). move/display text object at position, change its text

On mouse exit, just hide the text object.

I would choose this method since I can have this bit of code held in a master page, and the dataset will be able to span the whole publication.
If I add a new object to the publication, will only need to update the dataset with the values and the object to have the mouseover calling the overall script.