Okay, can I handle this in order like you did?

1. I'll check out the item tooltips, thanks. Did this happen on your character screen? I usually use sanity for dealing with this kind of thing, I haven't looked there in so long. I'll check it out though and see what I can learn. Also, when you got them to work, did you disable the entirety of TipOnDemand (/tod standby) or did you just uncheck delay?

2. You want .2 steps? I can do that! I'll get that in the next version.

3 & 4. With the logic confusion, could you explain further? I'll head into game and test a bit now but could you tell me how the logic differs from the logic ladder I explained in the description? What happens and when? For example, do whitelisted tooltips suddenly stop showing in combat or something like that? When you have them all enabled, tell me what you expect to be happening and what's not happening. I'm sorry for burdening you with this but I don't quite follow at the moment, I will do some testing in game though to see if anything's out of whack with how the logic ladder is supposed to work.

As I understand it though, you have delay, key, movement and combat on. So here's how it should work and this is what I'll be testing for ...

- All tooltips should hide at all times by default.
- If the modifier is held then the tooltips should delay for the set amount of time before showing if standing still.
- If moving or in combat, no tooltips will show as the logic ladder stops there and dismisses any further steps. The only tooltips which will show are whitelisted tooltips which are above combat on the ladder.

(Edit)

Okay, confirmed the character equipment thing, looking into it.

Also, I'll have to make a change so that only key, invert or delay can be enabled at one time, since I think that's what's causing the problems. The thing is you see that key shows the tooltip immediately but holding the modifier to do that also unhides the delayed tooltip. The only way to stop that would be to remove SetKey but Key needs SetKey to work.

(Edit)

I could always remove the 'hold modifier to show' element of the display module, if you like?

(Edit)

Okay, here's what I'm going to do, I think ...

- Put an exclusions list in delay for frames that don't work with it (such as PaperdollFrame).
- Put a hardlock on Stationary like with combat so it doesn't ever proceed down the ladder.
- Remove the modifier behaviour from the delay as that would help with the Key issue.

Those three should solve all the problems. I hope.

There y'go wraith! Give that a go and let me know what you think once you've tried it, feedback is always appreciated.

Here are some thoughts off the top of my head...

I would've implemented a fade-in but it's a lot of code to get it in there, for the option and then for the fade itself. I'm also not sure whether I trust Blizzard's FrameXML UIFadeFrame() function set to not lag the game, so I might end up writing my own for such a feature, which'd be a lot more code. So I leave this in your hands, would you prefer a fade-in as an option to popping up or would that just be bloat?

How's the limit and steps? Should the step be 0.1 instead of 0.2, should the limit be higher? The reason I used that step and that limit was because it made it easy to set, with a low step and a high upper limit, those sliders can be a git to get on just the right setting that you want. If you don't feel the limit and step are right, do you have any suggestions?

I've just been giving this some thought and... doy.

I don't have to stop the tooltip from showing and delay it, that doesn't have to happen. I need just hide it visually, right? After all, this might not be perfect for all scenarios because of clickable tooltips (accidentally hitting those in battle is a pain) but for simple five or so second delays, I just make it not visible. Would that work? I'll knock together a quick plugin now so you can test and what's more, this won't even mess with the existing logic. Hooray!

Thanks wraith.

I'll start researching into possible ways of implementing delays, now. Don't get your hopes up because it might very well be impossible but that doesn't mean I won't try.

Ooh, hm. That's a strange one. Do me a favour?

In the TipOnDemand_FuBar.lua file, after line 21 add...

self.folderName = "TipOnDemand"

See if that works?

Whoops, yeah. I used Bartender to figure out how to properly modularise the FuBar element, I had issues with it missing certain options (like position) so I had to refer to that. That was one object call I didn't rename. Just head into the file and change Bartender3 to T and it'll work fine. Sorry about that.

Hokay, just did a lot of work on TipOnDemand and I found out a few things, some of those things are good and some of those things are ... well, not quite so good.

First of all, the good. Skoo, take a look at the fourth milestone and tell me what you think, I think this new method is much more graceful than the clunky old self.status method and it won't cause modules to interfere with each other in unexpected ways, either. There shouldn't be any bugs here regardless since no variables are used, just returns.

Wraith, I'm sorry to say but after spending about two hours trying (egad) I just cannot find a way to make tooltips delay. Try it for yourself in game and see, hover over something which creates a tooltip (GameTooltip, not Tablet) and then type the following:

/script GameTooltip:Hide() GameTooltip:Show()

I don't know why it behaves like that that you can't make the tooltip show in the same instance as hiding it but that's how it is and it's bothering me because I know there has to be a way around that, I'll keep thinking about it but for the time being, the inclusion of tooltip delays does seem glum. If you know of another mod that does it then let me know, I'll take a look and see if I can get an idea about how to make this module work. I just don't want to create too much overhead though, since I've been going out of my way to keep TipOnDemand small and sensible but if you can supply a source and it can be implemented sanely, I'll do it. Otherwise... lots of thinking and experimentation for me.

For now though, I'm just glad to have m4 out there, I really am quite pleased with this one. I know there'll likely be bugs but I'm confident enough to call it R(elease) status so it's probably okay. If you do find bugs though, let me know and I'll get 'em fixed up.

Mostly I'm just happy that I won't have to be driven crazy by incorrect logic in my own work anymore...