This is what the usual tooltip-on-the-cursor type of addon will give you when you mouse over a frame
This is what Mousetip's per-button tooltip assignments allow you to do, so that no matter where your
This is Mousetip's options window, which you can show at any time with the /mousetip slash command
Cirk's Mousetip
What is Mousetip?
Mousetip is another show-the-tooltip-at-your-mouse-cursor type of addon (like TipBuddy, Tinytip, etc.) but written to have the features I particularly wanted from a tooltip addon:
It is a minimally intrusive as possible, and is written to work with the 2.0 (and now 3.0) clients from the ground up.
It introduces the concept of per-button tooltip positions, so that as you move your cursor over certain frames or buttons, Mousetip will actually place the tooltip in a settable location for that button, rather than keeping it on the cursor all the time (which is annoying when it gets in the way of what you are actually trying to look at!).
Feature-set wise, Mousetip is pretty lean compared to the likes of (say) TipBuddy:
Allows you to set the position of the tooltip either at the mouse cursor, or at a user placed anchor point.
Allows you to set an offset (horizontal and vertical) relative to the mouse
Allows you to change the scaling of the default game tooltips (and optionally of other tooltips that Mousetip knows about).
Allows showing a player's guild name in the tooltip (underneath the player name), and selecting the color that the guild names are shown in. (Also allows you to disable the showing of the guild name entirely if you don't like that feature of the default client).
Provides some simple tooltip coloring options for friendly, neutral, hostile, etc. targets. (I loved that feature in TipBuddy, so here it is again )
Allows setting the fade time for the tooltip.
Provides a simple target-of-target secondary tooltip that shows the appropriate target's name.
Allows you to show your standing (Neutral, Honored, etc.) with a faction next to their faction name
Per-button tooltip positions
For the per-button tooltip positioning, I've included only a few initial positions in Mousetip for the default WoW client's player, target, and party frames, and for the action buttons. However it is very easy to configure this for your own UI and tastes! For example, suppose you want to set Mousetip to show the tooltip to the right of your custom target frame. All you need to do for that is:
Move the mouse cursor over the target frame.
Do /mousetip set right.
Thats it! Well, actually there is a lot more that you can do if you really want to play around with it. See the full list of slash commands for more details.
Note that Mousetip will try and intelligently apply the per-button rules you give it, so that if you tell it (for example) that tooltips for the first party frame should be at the top-right of that frame, then Mousetip will apply that same position to all party frames (or at least all those that follow the usual naming rules).
Mousetip can also currently only set the tooltip position for a button or frame that would normally show the tooltip in the default bottom-right of your screen - it can't do anything about buttons or frames that set the tooltip location themselves (or that use their own custom tooltips).
Also, if you want to reset a particular button to use the cursor or use the default tooltip location (in the bottom right) just put the mouse over the button you want to change, and do /mousetip set cursor or /mousetip set default respectively. The default for frames that Mousetip doesn't know about is to use whatever you have set the default to in the options window (usually the normal bottom-right position of the default UI).
About the anchor point and alignment
Note that the anchor point and anchor alignment options will only be visible and changeable if either of the World tooltip position or the Default tooltip position are set to use the anchor. The anchor itself will also only be visible in this case, and only while the Mousetip options window is open.
The default location for the anchor is the bottom-right of your screen, near where the normal Blizzard default tooltip would appear. Look for a little red cross symbol.
Mousetip's slash commands
Mousetip supports the following slash commands:
/mousetip help shows this list of slash commands. /mousetip shows and hides the Mousetip options window. /mousetip on enables Mousetip. /mousetip off disables Mousetip. /mousetip set <position> sets where the tooltip will show for the frame or button that the mouse is currently hovering over. /mousetip set as <frame> indicates that tooltips for the frame or button that the mouse is currently hovering over should instead appear as if they were tooltips for the named frame. /mousetip set <frame> <position> sets where the tooltip will show for the named frame. /mousetip set <frame1> as <frame2> indicates that tooltips for the named frame1 should instead appear as if they were tooltips for the named frame2. /mousetip setparent indicates that tooltips for the frame or button that the mouse is currently hovering over should instead appear as if they were tooltips for the frame's parent. /mousetip id tells you the name of the frame or button the mouse cursor is currently hovering over, and the name of its parent frame as well. /mousetip id <frame> tells you the correctly capitalized name of the given frame, and the name of its parent frame as well. /mousetip reset tooltip resets the world and default tooltip position, alignment, anchor, and scaling. /mousetip reset colors resets the colors that Mousetip uses. /mousetip reset anchors resets the per-button tooltip anchors that you have entered. /mousetip reset all resets all of the tooltip, colors, and anchors. /mousetip list lists all the buttons and frames that Mousetip has been told to keep per-button settings for. /mousetip status shows the current status of Mousetip.
Enjoy!
-- Cirk
Change Log - Cirk's Mousetip
3.2.1
Made code more robust to attempted use on tooltip enabled frames without names, such as Elkano's BuffBars (thanks Vilkku)
Additional robustness changes for bad calling parameters and minor debug code cleanup
Fixed minor bug in order of names reported when using /mousetip set <frame1> as <frame2> option
Changed version string to 3.2.1.
3.2.0
Fixed a minor bug in the confirmation message shown when setting a frame to use another frame as its anchor.
Changed version string to 3.2.0.
3.1.0
Fixed a bug where /mousetip id would error if the hovered-over frame had no name.
Added an entry for Blizzard's interface options screen that shows a list of the slash commands, tidied up the help text, removed the normal addon "loaded" announcement in chat.
Changed version string to 3.1.0.
3.0.2
Greatly improved unit identification and handling - no more stuck tooltips!
Show tapped status before dead status (i.e., for on corpses)
Improved code efficiency for coloring unit names
Fixed bug where mouseover target's target's health wasn't being updated
Improved recognition of when the tooltip is no longer still valid
Fixed unexpected fadeout problem
Added a workaround for the problem of not recognizing frames that pretend to be the world frame but aren't (e.g., minimap zoom buttons)
Changed version string to 3.0.2
Reduced background color update delays to 0.2 second
Removed checking for UPDATE_MOUSEOVER_UNIT (this is now implicit with unit updates).
3.0.1
Fix issue that arises when logging in on a newly created character or after reinstalling WoW due to client messages arriving in unexpected order.
Changed version string to v3.0.1.
3.0.0
Added the option to show your characters standing next to each recognized faction in the tooltip.
Added default location for the FocusFrame
Added a scaling control suppression feature (needed by Targetz)
Bug fix for some tooltip alignment cases that weren't being handled correctly
Various changes for version 3.0 compatibility
Changed version string to v3.0.0.
2.3.0
Mousetip will save the itemref tooltip location on a per character basis to replace Blizzard's new mechanism for this (which is a bit broken).
Added hooking of the ValidateFramePosition function so we can restore scaling while it calculates frame positions (since it doesn't do this itself)
Save border color as well as background color when Mousetip changes those parameters for a tooltip.
Added use of an anchorTime field to the tooltip to allow Mousetip to identify when a tooltip is shown long after it is anchored and compensate for the normal lack of fading in this case (e.g., corpses).
Made Mousetip a little more robust to bad data passed to tooltip handlers from other addons.
Provide a Mousetip.SetTooltipColorForUnit function to allow other addons to have their tooltip colors updated based on a specific unit the same way that Mousetip normally does itself (now used by Targetz for example).
The /mousetip list command now shows all its entries in alphabetical order of the button names.
Miscellaneous code cleanups and rearranging (all functions contained in the Mousetip global now).
2.2.0
Modified logout code to only update settings if the player had actually logged in properly (fixes a bug in losing user settings)
Avoid calling scaling code in other (known) addons when they haven't fully initialized yet.
incompatibility between Mousetip and Dailies Quest Tracker
I'm not sure where the issue lies so I'm giving you both a heads up, but there is an incompatibility between Cirk's Mousetip and Dailies Quest Tracker.
When using Mousetip's scaling function it pretty much destroys DQT's tooltip, even if in Mousetip the scale all tooltips option is turned off.
It looks like it tries to put the bottom of the tooltip above the top, making it completely unreadable.
No other LDB addons I have seem to have any issues with it, though most aren't scaled by Mousetip either. Only DQT's tooltip has this weird behavior.
Originally posted by Cirk Updated Mousetip to v3.2.1 - changes are mostly to deal with the sort of scenario that Vilkku was encountering: trying to use Mousetip with tooltip enabled frames that have no name (such as the buff frames in Elkano's BuffBars).
Vilkku, if you still want to move the location of the tooltip for BuffBars, there is an option in BuffBars itself to do this, and that might do the job for you. (Otherwise you'll need to poke Elkano to give names to those tooltip frames )
Cheers
-- Cirk
Thanks for taking a look at this. And silly me for not exploring the EBB options enough, indeed, the tooltip options there work just as I'd like them to. Thanks for a great mod, keep up the good work!
Updated Mousetip to v3.2.1 - changes are mostly to deal with the sort of scenario that Vilkku was encountering: trying to use Mousetip with tooltip enabled frames that have no name (such as the buff frames in Elkano's BuffBars).
Vilkku, if you still want to move the location of the tooltip for BuffBars, there is an option in BuffBars itself to do this, and that might do the job for you. (Otherwise you'll need to poke Elkano to give names to those tooltip frames )
Dang, sorry Vilkku, I completely forgot about this one!
Basically I -think- the problem here is that the BuffBar buttons aren't being created with a name, and so the code in Mousetip for parsing the button name (to determine the pattern matching rule) throws an error.
I'll have a proper look at it tonight, see if I can figure out a work-around/solution for it, or at least modify it so it doesn't fall over with that error.
This has been sitting in the bug report thingie for some time now. Is there noting you can do to fix it or did you simply miss it?
Quote:
Elkano's BuffBars set their tooltip to the Blizzard default position. For other tooltips which have done this, I've been able to get them to the cursor using the command
/mousetip set topright
while hovering the cursor over the frame. However, when I do this for the BuffBar frame I get the following error:
[20:21:01] Interface\AddOns\Mousetip\Mousetip.lua:1172: bad argument #1 to 'reverse' (string expected, got nil)
[C]: ?
[C]: in function `reverse'
Interface\AddOns\Mousetip\Mousetip.lua:1172: in function `SetAnchorPattern'
Interface\AddOns\Mousetip\Mousetip.lua:1315: in function `ProcessSetButton'
Interface\AddOns\Mousetip\Mousetip.lua:3023: in function `SlashCommand'
Interface\AddOns\Mousetip\Mousetip.lua:2215: in function `?'
Interface\FrameXML\ChatFrame.lua:3332: in function <Interface\FrameXML\ChatFrame.lua:3285>
[C]: in function `ChatEdit_ParseText'
Interface\FrameXML\ChatFrame.lua:3052: in function `ChatEdit_SendText'
Interface\FrameXML\ChatFrame.lua:3073: in function <Interface\FrameXML\ChatFrame.lua:3072>
[C]: in function `ChatEdit_OnEnterPressed'
[string "*:OnEnterPressed"]:1: in function <[string "*:OnEnterPressed"]:1>
Updated Mousetip to 3.1.0. Only one minor bug fix (for the /mousetip id command), added an entry for Mousetip to the Blizzard interface addons page, updated the help text a bit, and removed the "loaded" announcement.
Originally posted by Potter Riddle me this dear sir..
...
Hi Potter - mousetip already has the ability to show the target of your tooltip (mouseover) target, although it only shows the name of the mouseover target in the second tooltip. Are you asking for the target tooltip to have more than just the name, or ?
Re: Mousetip v3.0.2 - fix for the stuck tooltip...
Quote:
Originally posted by Cirk Septikron got me thinking again about the stuck tooltip problems, and so I did a lot more digging and experimenting with some of the things that changed in the 3.0 patch, and, well, end result is I think I've finally got it nailed in 3.0.2.
Its not all perfect - there's another "bug" in the Blizzard default logic that can result in the tooltip's unit name color being wrong, where it shows up as the default gold color for a brief moment (maybe less than half a second). Near as I can figure, that happens with the default Blizzard code too! One day maybe they'll change some internal mechanism and we can fix this one too, but it shouldn't appear too often at any rate, and its only momentary when it does, so hopefully no-one will even notice
Enjoy!
-- Cirk
Don't suppose it'd be possible for you to release just the positioning code as a separate addon?
I really like the idea of smart positioning, but I have another ToolTip that I really enjoy using. I'd love to be able to use your smart position mixed w/ the other tooltip.
Septikron got me thinking again about the stuck tooltip problems, and so I did a lot more digging and experimenting with some of the things that changed in the 3.0 patch, and, well, end result is I think I've finally got it nailed in 3.0.2.
Its not all perfect - there's another "bug" in the Blizzard default logic that can result in the tooltip's unit name color being wrong, where it shows up as the default gold color for a brief moment (maybe less than half a second). Near as I can figure, that happens with the default Blizzard code too! One day maybe they'll change some internal mechanism and we can fix this one too, but it shouldn't appear too often at any rate, and its only momentary when it does, so hopefully no-one will even notice
Originally posted by septikron I've noticed that the tooltip sometimes 'sticks' to the cursor long after I'm no longer hovering over a corpse. In particular, 'skinnable' corpses seem to remain on the curosr until I mouse over something else.
Yeah septikron, this is basically because Mousetip has to "fake" the fadeout of the tooltip (since Blizzard didn't give us a function to set the delay and fade and without that we'd be stuck with 1 second delay and then a 1 second fadem which is fine for an anchored tooltip, but annoying on the cursor). In particular, as you've noted, there are some cases (on corpses most commonly, but also when players move off the cursor before it gets an update) where all the tricks I've put in place to handle this stuff still can't quite identify.
Interestingly too, I've noticed that sometimes Blizzard's own tooltip code has the same problem (e.g., if I blow away the cache, use no addons, and then login and mouse over a player corpse quickly, the tooltip comes up and stays up).
One day I'll figure out a bullet-proof solution (or Blizz will add controllable fade timing to the tooltip ) but for now its just a (hopefully small) annoyance.
I've noticed that the tooltip sometimes 'sticks' to the cursor long after I'm no longer hovering over a corpse. In particular, 'skinnable' corpses seem to remain on the curosr until I mouse over something else.
)
