For some reason Skinner seems to be lowering the alpha of the combat log text both on the combat log frame and on the worldmap frame. I've had to disable skinning of both frames in order to be able to read the text on them.
I checked the two text color settings in Skinner's color menu, and they're set to full opacity.
Having this same issue with the questframe as well, cannot read the text of the quest to accept in the frame.
1x Skinner-b2.11159.2\UIElements2.lua:387: attempt to index field 'frames2ignore' (a nil value)
(tail call): ?:
<in C code>: ?
Skinner-b2.11159.2\Skinner.lua:800: in function <Skinner\Skinner.lua:798>
Skinner-b2.11159.2\Skinner.lua:812: in function `checkAndRun'
Skinner-b2.11159.2\AddonFrames.lua:227: in function <Skinner\AddonFrames.lua:220>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Ace3):164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
---
The following should work if you update "Interface\AddOns\Skinner\SkinMe\tabDB.lua" with it.
function Skinner:tabDB()
if ( libTab ) then
if ( libTab.Data.TabDBtabs ) then -- version 2.0a1
for k, v in pairs(tabDB_tabFrames) do
local tabId = libTab.Data.TabDBtabs.tab["fid_"..v.Frame]
local tabObj = _G["libTabTabDBtabs"..tabId]
self:removeRegions(tabObj, {1})
if ( v.Frame == "LFDParentFrame" ) then
libTab.Data.TabDBtabs.tab[tabId].offsetX = 0 -- We no longer need an offset for this frame when using Skinner
end
end
elseif ( libTab.Data.TestTabs ) then -- version 2.0a
for k, v in pairs(tabDB_tabFrames) do
local tabId = libTab.Data.TestTabs.tab["fid_"..v.Frame]
local tabObj = _G["libTabTestTabs"..tabId]
self:removeRegions(tabObj, {1})
if ( v.Frame == "LFDParentFrame" ) then
libTab.Data.TestTabs.tab[tabId].offsetX = 0 -- Same as above
end
end
end
else
for i = 1, TABDB_MAX_TABS do -- version 1.0a
local tabObj = _G["tabDBtab"..i]
self:removeRegions(tabObj, {1}) -- N.B. other regions are icon and highlight
end
end
end
The following should work if you update "Interface\AddOns\Skinner\SkinMe\tabDB.lua" with it.
function Skinner:tabDB()
if ( libTab ) then
if ( libTab.Data.TabDBtabs ) then -- version 2.0a1
for k, v in pairs(tabDB_tabFrames) do
local tabId = libTab.Data.TabDBtabs.tab["fid_"..v.Frame]
local tabObj = _G["libTabTabDBtabs"..tabId]
self:removeRegions(tabObj, {1})
if ( v.Frame == "LFDParentFrame" ) then
libTab.Data.TabDBtabs.tab[tabId].offsetX = 0 -- We no longer need an offset for this frame when using Skinner
end
end
elseif ( libTab.Data.TestTabs ) then -- version 2.0a
for k, v in pairs(tabDB_tabFrames) do
local tabId = libTab.Data.TestTabs.tab["fid_"..v.Frame]
local tabObj = _G["libTabTestTabs"..tabId]
self:removeRegions(tabObj, {1})
if ( v.Frame == "LFDParentFrame" ) then
libTab.Data.TestTabs.tab[tabId].offsetX = 0 -- Same as above
end
end
end
else
for i = 1, TABDB_MAX_TABS do -- version 1.0a
local tabObj = _G["tabDBtab"..i]
self:removeRegions(tabObj, {1}) -- N.B. other regions are icon and highlight
end
end
end
For some reason Skinner seems to be lowering the alpha of the combat log text both on the combat log frame and on the worldmap frame. I've had to disable skinning of both frames in order to be able to read the text on them.
I checked the two text color settings in Skinner's color menu, and they're set to full opacity.
It is skinned however (im looking at it right now, fully skinned apart from buttons that haven't been updated), it probably uses some "shared" config method that is being skinned separately.
It is skinned however (im looking at it right now, fully skinned apart from buttons that haven't been updated), it probably uses some "shared" config method that is being skinned separately.
Erm. Mine is not, what versions of both addons are you using?
Skinner-b2.11159.2\UIElements1.lua:505: attempt to index field '?' (a nil value)
(tail call): ?:
<in C code>: in function `WorldMapFrame_ToggleAdvanced'
<string>:"*:OnLoad":3: in function `setFunc'
Interface\FrameXML\InterfaceOptionsPanels.lua:90: in function <Interface\FrameXML\InterfaceOptionsPanels.lua:86>:
<in C code>: in function `pcall'
Interface\FrameXML\InterfaceOptionsFrame.lua:217: in function <Interface\FrameXML\InterfaceOptionsFrame.lua:216>:
<in C code>: in function `securecall'
Interface\FrameXML\InterfaceOptionsFrame.lua:252: in function <Interface\FrameXML\InterfaceOptionsFrame.lua:248>:
<in C code>: in function `Click'
Interface\FrameXML\UIParent.lua:2880: in function `ToggleGameMenu':
<string>:"TOGGLEGAMEMENU":1: in function <[string "TOGGLEGAMEMENU"]:1>
Locals:
(*temporary) = "down"
(*temporary) = 1
(*temporary) = -1
(*temporary) = 0
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = <function> defined =[C]:-1
---
Having this same issue with the questframe as well, cannot read the text of the quest to accept in the frame.
Sure, if I can remember to. I haven't been playing WoW as much lately.
The following should work if you update "Interface\AddOns\Skinner\SkinMe\tabDB.lua" with it.
Ready checks work just fine and if I delete the ORA3.LUA from the \skinme directory, it works just fine and I can see the results of the checks.
Anyone else seeing this issue? (I am running the latest beta of both).
Thx.
Here's what I'm talking about:
Look at the text in the lower left corner of the worldmap frame.
Gathermate should be skinned
Can't find a skin for it in AddonSkins.
Erm, what's the problem with unticking skinning of nameplates in config?
It is skinned however (im looking at it right now, fully skinned apart from buttons that haven't been updated), it probably uses some "shared" config method that is being skinned separately.
http://wow.curse.com/downloads/wow-addons/details/gupcharacter.aspx
Merry Christmas everyone!
Erm. Mine is not, what versions of both addons are you using?