Authors CurseForge

Hi,

Version b7.22423.1

However might also have something to do with me disabling the Blizzard compact raid frame UI. Maybe add check to only attempt to skin if Blizzard_CompactRaidFrames is enabled?

1x Skinner\PlayerFrames.lua:832: attempt to index field 'CompactRaidFrameContainer' (a nil value)
(tail call): ?
[C]: in function `xpcall'
Skinner\UtilFuncs.lua:180: in function <Skinner\UtilFuncs.lua:174>
(tail call): ?
Skinner\AddonFrames.lua:266: in function `?'
...er_DurabilityInfo\Libs\AceTimer-3.0\AceTimer-3.0-17.lua:53: in function <...er_DurabilityInfo\Libs\AceTimer-3.0\AceTimer-3.0.lua:48>

Locals:
nil

Transmog window when moving the character "doll" 3D image around (mouse click and drag left or right) it makes a repetitive clicking sound. The same sound it makes when you use the navigation buttons above that doll image. This does not happen in the character window, inspect window, or dressing room window

This seems to be skinned via the "Collections Journal"

Reference

Quote from transitbus

Version b7.22423.1

However might also have something to do with me disabling the Blizzard compact raid frame UI.

/snip

Hi transitbus,

Quote from Shimiya

Hi Jncl,

Is there a way to set UI buttons borders to have same appearance/size/width than frames borders ?

/snip

Hi Shimiya,

Quote from Jncl

Hi transitbus,

How do you disable the Blizzard Compact Raid Frame UI?

I do and that's why this error is happening. It's ok if you don't want to check to make sure the blizzard compact raid frame addon is enabled and if not uncheck the options that hook into it but I just wanted to report this as there are several users like myself who don't use the default raid frame UI and disabled the blizzard addons to prevent taint issues.

Edit: lol did not read the "how do you"

I disabled them at the addons.txt level on my wtf character file so they are disabled unless I reenable them.

Commonly, I use Ketho's macro script to quickly disable or enable them

/run local f = IsAddOnLoaded("Blizzard_CompactRaidFrames") and DisableAddOn or EnableAddOn for _, v in pairs({"Blizzard_CompactRaidFrames", "Blizzard_CUFProfiles"}) do f(v) end ReloadUI()

Quote from Shimiya

Sorry, I have not been clear.

I was talking about "Game menu" buttons borders on my screenshot, which are correctly skinned/class coloured by skinner, but are thicker than other borders regardless of any settings (not about items in my bags, it's just for show you the "closing button cross" which have also the thicker border).

Hi Shimiya,

Quote from transitbus

/snip
but I just wanted to report this as there are several users like myself who don't use the default raid frame UI and disabled the blizzard addons to prevent taint issues.

/snip

Hi transitbus,

Hi,

Quote from Jncl

Hi transitbus,

I wasn't aware that this could be done. I will check AddOn info and only skin AddOns that are 'loadable'. Are there any other Blizzard AddOns that you or others disable?

that's the only one I am disabling outside of the corresponding Blizzard_CUFProfiles but I do not think that is in anyway so meting that would negatively impact skinner.

So the latest released fixed my two issues I posted which is awesome. Now I wonder if you could do something on your toc file to avoid forcing library downloads form the curse client and installs of them?

In skinner.toc you have

## OptionalDeps: Ace3, LibSharedMedia-3.0, AceGUI-3.0-SharedMediaWidgets, LibBetterBlizzOptions-1.0

This forces the install if you auto update skinner via curse (I know, you should really download skinner manually). This isn't in the nolib version btw.

Could you remove those optional dependencies since you already include them in the toc file and in the libs directory?

And one more of note. Skinning the what's new window removes all artwork, which half the window is composed of.

Instead of looking like the left with the background skinned, it looks like the right with no artwork at all.

Quote from transitbus

And one more of note. Skinning the what's new window removes all artwork, which half the window is composed of.

Instead of looking like the left with the background skinned, it looks like the right with no artwork at all.

Hi transitbus,

Quote from transitbus

/snip

In skinner.toc you have

## OptionalDeps: Ace3, LibSharedMedia-3.0, AceGUI-3.0-SharedMediaWidgets, LibBetterBlizzOptions-1.0

This forces the install if you auto update skinner via curse (I know, you should really download skinner manually). This isn't in the nolib version btw.

Could you remove those optional dependencies since you already include them in the toc file and in the libs directory?

Hi transitbus,

Quote from Jncl

Hi transitbus,

If you auto-install via the Curse App, I thought you could specify the no-libs option for the AddOn.

The packager puts them in the Libs directory based upon the .pkgmeta.txt contents, not AFAIK the OptionalDependencies entry in the TOC file

First, thanks for the answer about the what's new frame. I just keep it unskinned so that's not an issue for me and makes dense as to why it does that (was afraid so).

As far as the library installation, this is just an assumption, I think that optional dependency line is making the client tick the "install library separately" on skinner. I don't select no lib installed by default so that's my only thought as to why it trie to do it with skinner. Un-ticking that in the client resolved it for now and I'll just ensure it doesn't tick that should I want to update via the client. Skinner is the only addon that has done that for me so I was a tad concerned but at least I have a work around ;)

More issues: dropdown menus (I assume all backdrop borders as well) seem to not be rendering border textures correctly. I am using the skinner border texture but any valid texture will do the same.

Here is an example of it rendering the texture wrong on the skinner interface option and on pitbull unit frames




this happens even with all addons disabled but skinner