<Funkeh`> when you make quicklauncher, most people WILL want hints
<Funkeh`> left click to X
<Funkeh`> right click to X
<Funkeh`> I don't think just because an object has a tip, it isn't a launcher
<Funkeh`> that's silly
<Tekkub> Then use it :P I don't see why it has to be written into the spec before you use it
Basically what the discussion is that any launcher can have a tooltip.
I just switched from fubar to Fortress & FuBar2Broker and the tooltips seem a bit large. Specifically this is for the ZOMGBuffs and ClosetGnome tooltips that also serve as menus.
Where do I look if I want to scale down the tooltips of my "Blocks?" Thanks!
The idea is for them to drop FuBarPlugin (and all it's embeds) and instead use LDB for their launchers. And have someone write an addon that renders them on FuBar for the users that want em there... problem so far is that the people interested in LDB are interested because the DON'T want to use Fu.
So if I wanted a launcher for Omen and Recount I'd have to edit their .lua and embeds.xml files?
Quote from tekkub »
The idea is for them to drop FuBarPlugin (and all it's embeds) and instead use LDB for their launchers. And have someone write an addon that renders them on FuBar for the users that want em there... problem so far is that the people interested in LDB are interested because the DON'T want to use Fu.
If it's not actually embedding FBP then I guess there's not much issue. Still it would be trivially easy to add LDB launchers in so people don't have to use FuBar2LDB *grin*
My current plan is to use the LDB design here. Make "Cork" just a display, renders a tooltip-like frame you can click-cast from. Then split all the buff and other crap out into plugins that use LDB to communicate with the core display.
The biggest hurdle is getting rid of SEAura. I'm working on creating a cache for the aura checks instead of scanning and firing events. In short, the cache for a unit's auras is cleared when the respective event fires. The first time after that a query is made, that unit is scanned and saved. Still not sure how exactly to handle raid roster updates without it becoming spammy though.
I wish I could provide a little insight on the SEAura problem, but I don't think I'd be of much help there.
On a side note (and perhaps this belong elsewhere), I generally run with the CorkFu tooltip detached. I'm assuming that sort of functionality would be the responsibility of the data display, correct? Wouldn't data feeds using .tooltiptext run afoul of this due to their reliance on GameToolTip?
There will be no tooltip. Cork will make it's own frame. I'm talking about using a new LDB spec here, not providing a data feed thru LDB (although I'll probably do that as well).
I don't know if this applies to other intercepted fu mods with drop down menus, but Wardrobe2's dropdown, or rather the dropdown's sub-menus. don't work properly. For instance, right click the wardrobe2 display for the main menu, scroll to update/delete/mounted, and then.... nothing. It's suppose to pop out a list of your saved sets, so youcan just select them to update/delete/setmounted quickly.
There are always slash commands, that's fine. But I was just getting this out there to see if there's a fix/workaround, and/or check to see if it might be affecting other addons as well.
I know that someone will scream at me for asking something that stupid, but... what does makerocketgonow do? I tried to figure out the README and tried installing it, but I still have no idea what it actually does. ^_^*
Basically what the discussion is that any launcher can have a tooltip.
You beautiful, beautiful man. Will start testing now.
Where do I look if I want to scale down the tooltips of my "Blocks?" Thanks!
So if I wanted a launcher for Omen and Recount I'd have to edit their .lua and embeds.xml files?
What embeds? =D
If it's not actually embedding FBP then I guess there's not much issue. Still it would be trivially easy to add LDB launchers in so people don't have to use FuBar2LDB *grin*
I'm still working on Cork (no-fu) bit by bit. It's slow going though because I'm not exactly sure how I want to redesign it.
Yeah, I know. Unfortunately, the dead and rotting corpse of CorkFu is still superior to anything else out there. I'm just biding the time.
My current plan is to use the LDB design here. Make "Cork" just a display, renders a tooltip-like frame you can click-cast from. Then split all the buff and other crap out into plugins that use LDB to communicate with the core display.
The biggest hurdle is getting rid of SEAura. I'm working on creating a cache for the aura checks instead of scanning and firing events. In short, the cache for a unit's auras is cleared when the respective event fires. The first time after that a query is made, that unit is scanned and saved. Still not sure how exactly to handle raid roster updates without it becoming spammy though.
On a side note (and perhaps this belong elsewhere), I generally run with the CorkFu tooltip detached. I'm assuming that sort of functionality would be the responsibility of the data display, correct? Wouldn't data feeds using .tooltiptext run afoul of this due to their reliance on GameToolTip?
There are always slash commands, that's fine. But I was just getting this out there to see if there's a fix/workaround, and/or check to see if it might be affecting other addons as well.
Pretty handy. Think Quickie as a button rather than a pop-in from off frame.
Which addons have launchers? I have yet to encounter a single one (that I use).