FuBarPlugin:OpenTooltip should not get called, because currentTip[addon] should be nil (in addon.UpdateTooltip).
Maybe I'm not seeing something, but currentTip[addon] gets set on every OnEnter of the broker plugin and is never nil'd out.
However, I did insert some debug logging inside of addon.UpdateTooltip and noticed that normally it only calls OpenTooltip if the tooltip/tablet is already visible.
I'm just wondering if the code is flaking out in some cases due to bad assumptions, because I don't understand what's going on enough to rule it out.
OK. I'm currently testing F2B r73, and so far so good. I just hearthed, and despite the hearthstone cooldown ticking away in the TransporterFu tooltip, I can view other addon's tooltips without them disappearing (or closing and having the TransporterFu tooltip open instead).
So I'm wondering if the issue with phantom tooltips appearing is because F2B's OnEmbedEnable() method is calling FuBarPlugin:OpenTooltip() as part of its addon.UpdateTooltip handling, which now in turn calls tablet:Open().
I had this issue with Expo + ButtonBin and I fixed it. The fix I made was to only call tablet:Open if the callback is from the OnEnter event. When UpdateTooltip is called the tooltip shouldn't be opened if it isn't already.
OK. I'm currently testing F2B r73, and so far so good. I just hearthed, and despite the hearthstone cooldown ticking away in the TransporterFu tooltip, I can view other addon's tooltips without them disappearing (or closing and having the TransporterFu tooltip open instead).
Though my system was out of commission for the last 2 days (thanks to a corrupted Windows Explorer and subsequent upgrade to Vista), I have yet to encounter any issues as I was previously, since upgrading to r73.
So my conclusion is that the problems are indeed fixed.
Enabling, Disabling and Locking the bars seems to behave strangely. If I lock the bar, all the disabled broker addons appear ... though they are still marked as disabled.
Enabling, Disabling and Locking the bars seems to behave strangely. If I lock the bar, all the disabled broker addons appear ... though they are still marked as disabled.
Thanks for the report, this should be fixed in the new alpha.
Is there any way to create "empty" blocks (to bind together blocks and get space between then but still have them react to eachother when other blocks changes size)
I'd love this option, too. (Searched through the thread and didn't find an answer to this.)
I'm trying to move away from Fubar and while Fortress seems like it might work for me (with a whole lot of configuration to mimic Fubar), it's still not quite what I'm looking for. I've also tried Button Bin but that addOn lacks a Center justification. My old Fubar setup had bars across the top and bottom buttons on the left, center and right, all justified and spaced accordingly. I'm trying to adapt. I actually like messing my interface :)
it seems that some ldb addon now use a texcoord argument to modify the texture used for the icon.
picoButtons by tekkub is an example.
Can you please use this texcoord argument to properly display the icon as intended by the author of the plugin?
.texcoord is not in the official spec, but I'll look for some information about this. I'm not yet sure that this is added, as the LegoBlock lib (used for the blocks) does not support TexCoord, so some hacks may be needed.
.texcoord is not in the official spec, but I'll look for some information about this. I'm not yet sure that this is added, as the LegoBlock lib (used for the blocks) does not support TexCoord, so some hacks may be needed.
I modified Fortress on my local copy to test texcoord and it's working, in red what I've added.
local uniqueUpdaters = {
text = TextUpdater,
icon = function(frame, value, name)
if value and GetPluginSetting(name, "showIcon") then
frame:SetIcon(value)
frame:ShowIcon()
else
frame:HideIcon()
end
end,
[COLOR=Red] texcoord = function(frame, value, name)
local object = dataObjects[name]
if object.texcoord then
frame.icon:SetTexCoord(unpack(object.texcoord))
end
end,
[/COLOR]
-- tooltiptext is no longer in the data spec, but
-- I'll continue to support it, as some plugins seem to use it
tooltiptext = function(frame, value, name)
local object = dataObjects[name]
local tt = object.tooltip or GameTooltip
if tt:GetOwner() == frame then
tt:SetText(object.tooltiptext)
end
end,
}
Hi!
maybe since last update, i ve one curious issue...
when i desactivate one LDB in fortress, i can't activate it more..because i can't acces first option page, but just second.
so i can't check "activate" to see LDB again. i desactivated bartender4 because no need but now i would like to see it again, i can't ..
PS: i tried to delete savevariable but no good change.
Hi!
maybe since last update, i ve one curious issue...
when i desactivate one LDB in fortress, i can't activate it more..because i can't acces first option page, but just second.
so i can't check "activate" to see LDB again. i desactivated bartender4 because no need but now i would like to see it again, i can't ..
PS: i tried to delete savevariable but no good change.
Same problem since forever.
I'm not very dependent on Fortress so I've resorted to using the individual addon configuration options where available.
Same problem since forever.
I'm not very dependent on Fortress so I've resorted to using the individual addon configuration options where available.
Ahhh, it's curious because i am not sure but i change very often me ui and i was thinking i could before.
anyway, if i disable one broker inside fortress, and for some reason, i have to use it again, i find the issue to go in savevariable, and change false to true for the broker i need :p
Hello i like Fortress but i have an annoing visual glitch wenn i hover a Broker plugin that is not from Tekkub or a Fubar plugin, then the Tooltip is flickering.
as far as i know tekkub uses his one tooltip lib tektip.lua to create the tooltip amd I use Fubar2Broker for the Fubar Plugins
so Tekkubs Addons and the Fubar Plugins dont flicker at all but the other tooltips do.
The disabled brokers bug was fixed some times ago, but the fix seems to be lost. It'll work in the next alpha version, that will be released as soon as the repository works again.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Maybe I'm not seeing something, but currentTip[addon] gets set on every OnEnter of the broker plugin and is never nil'd out.
However, I did insert some debug logging inside of addon.UpdateTooltip and noticed that normally it only calls OpenTooltip if the tooltip/tablet is already visible.
I'm just wondering if the code is flaking out in some cases due to bad assumptions, because I don't understand what's going on enough to rule it out.
So far, so good.
I had this issue with Expo + ButtonBin and I fixed it. The fix I made was to only call tablet:Open if the callback is from the OnEnter event. When UpdateTooltip is called the tooltip shouldn't be opened if it isn't already.
It works for me.
So, it's actually working as it should? :eek:
So my conclusion is that the problems are indeed fixed.
Thanks again, for everyone's work on this!
Thanks for the report, this should be fixed in the new alpha.
Thank you!
I'd love this option, too. (Searched through the thread and didn't find an answer to this.)
I'm trying to move away from Fubar and while Fortress seems like it might work for me (with a whole lot of configuration to mimic Fubar), it's still not quite what I'm looking for. I've also tried Button Bin but that addOn lacks a Center justification. My old Fubar setup had bars across the top and bottom buttons on the left, center and right, all justified and spaced accordingly. I'm trying to adapt. I actually like messing my interface :)
Any help appreciated!
picoButtons by tekkub is an example.
Can you please use this texcoord argument to properly display the icon as intended by the author of the plugin?
I'll add this option.
.texcoord is not in the official spec, but I'll look for some information about this. I'm not yet sure that this is added, as the LegoBlock lib (used for the blocks) does not support TexCoord, so some hacks may be needed.
I modified Fortress on my local copy to test texcoord and it's working, in red what I've added.
It seems LegoBlock isnt messing with the icon. Thanks for the code:)
maybe since last update, i ve one curious issue...
when i desactivate one LDB in fortress, i can't activate it more..because i can't acces first option page, but just second.
so i can't check "activate" to see LDB again. i desactivated bartender4 because no need but now i would like to see it again, i can't ..
PS: i tried to delete savevariable but no good change.
Same problem since forever.
I'm not very dependent on Fortress so I've resorted to using the individual addon configuration options where available.
Ahhh, it's curious because i am not sure but i change very often me ui and i was thinking i could before.
anyway, if i disable one broker inside fortress, and for some reason, i have to use it again, i find the issue to go in savevariable, and change false to true for the broker i need :p
as far as i know tekkub uses his one tooltip lib tektip.lua to create the tooltip amd I use Fubar2Broker for the Fubar Plugins
so Tekkubs Addons and the Fubar Plugins dont flicker at all but the other tooltips do.