Authors CurseForge

Quote from Fritos »

I was on my flying mount in Shatt, flew to the Flight Path master. As soon as the Flight Path frame started shrinking my client crashed.

If you can reproduce it I'd be interested, but at this point it likely didn't have anything to do with the mod.

Your probably right, tried it numerous times now with no issues. Odd, though. Never had a client crash before. Must'a been a fluke.

Thanks. :)

Quote from OttoDeFe »

Good Morning!

Enjoying the Bejezuz outta this. I do have 2 small issues:
The Baggins support seems to leave my search bar on screen when I minimize.
This error appears intermittently on a second opening of bags at bank/mailbox:

[2007/09/11 04:49:54-63-x3]: Interface\FrameXML\ContainerFrame.lua:616: attempt to compare number with nil:
Interface\FrameXML\ContainerFrame.lua:664: in function `ContainerFrameItemButton_OnUpdate':
<string>:"*:OnUpdate":1: in function <[string "*:OnUpdate"]:1>

Thanx!

I'll look into the first after work today. Should be working now.

The second is a Blizzard bug that's fixed on PTR.

Took another look -more closely- at this.

With Advanced TradeSkill Window, VisualThemes opens up Blizzard's default skill window as well as ATSW (it was that window not TradeJunkies that opened).

I'm not sure if this happens with other trade addons as I don't use any other than ATSW.

So again, not an error just something cosmetic to look at when everything else is sorted.

Still can't believe you managed this inside WoW! Simply loving it. :)

Quote from SirQuester »

Took another look -more closely- at this.

With Advanced TradeSkill Window, VisualThemes opens up Blizzard's default skill window as well as ATSW (it was that window not TradeJunkies that opened).

I'm not sure if this happens with other trade addons as I don't use any other than ATSW.

So again, not an error just something cosmetic to look at when everything else is sorted.

Still can't believe you managed this inside WoW! Simply loving it. :)

Probably a simple fix, looking into it after tonight's raid.

Quote from OttoDeFe »

The search bar now disappears...

BUT:
"Dewdrop-2.0-48630 (DewdropLib):790: Dewdrop20Button1:SetPoint(): Dewdrop20Level2 is dependent on this\n\n ---",

from several different buttons. Error doesn't appear when VH disabled. Also, it seems to interfere w/ Prat's editbox. Can't seem to type letters unless I click on it, but / and ] (symbols) work fine. Again, w/o VisualHeal, these issues don't show.

A Pain ain't I? ;^

Very strange, I'll look into it but if VH is doing something strange there might not be too much I can do. ;/

Excellent job on this addon! I've been wishing for some functionality like this for a long time, and was planning on writing something to do it, but it looks like you've got something going on already.

A bug that happened today, when you close the chat edit box (by submitting it, or hitting Esc) and quickly reopening it before it fully fades away (by hitting Enter or /), the chat edit box will display again, however the focus is not on the edit box, so any keys pressed will behave as if you're not typing into the chat edit box. Hitting Esc will not close it (it will bring up the Main Menu - normal behavior without the edit box). Also hitting Enter will not focus on it, nor submit it, so it still stays up, hitting the slash key (/) will put a slash in the box, but will still not focus on it. In order to focus on it, and close the box, you have to actually click on the edit box.

Quote from so2 »

Excellent job on this addon! I've been wishing for some functionality like this for a long time, and was planning on writing something to do it, but it looks like you've got something going on already.

A bug that happened today, when you close the chat edit box (by submitting it, or hitting Esc) and quickly reopening it before it fully fades away (by hitting Enter or /), the chat edit box will display again, however the focus is not on the edit box, so any keys pressed will behave as if you're not typing into the chat edit box. Hitting Esc will not close it (it will bring up the Main Menu - normal behavior without the edit box). Also hitting Enter will not focus on it, nor submit it, so it still stays up, hitting the slash key (/) will put a slash in the box, but will still not focus on it. In order to focus on it, and close the box, you have to actually click on the edit box.

I saw this happen tonight just a few minutes ago also. Definitely trying to get this fixed ASAP. Also seeing the dewdrop SetPoint error, working on it.

If anyone can reliably reproduce the

(DewdropLib):790: Dewdrop20Button1:SetPoint(): Dewdrop20Level2 is dependent on this

error I'd be very interested in a detailed report, try as I might I cannot seem to reproduce it intentionally.

Quote from SirQuester »

Took another look -more closely- at this.

With Advanced TradeSkill Window, VisualThemes opens up Blizzard's default skill window as well as ATSW (it was that window not TradeJunkies that opened).

I'm not sure if this happens with other trade addons as I don't use any other than ATSW.

I changed it to simply disallow the Craft and Tradeskill frames to be themed when Advanced TradeSkill Window is loaded. In the process I also added Advanced TradeSkill Window frames to be themed.

Quote from X-buZZ »

I have a little request: Would it be possible to add theme support fpr ArkInventory?

I'll look into supporting it tonight.


Also for the ChatEditBox I'm looking into an alternate method that will hopefully avoid all of the previous issues with it. Over the weekend I should be able to finish the GUI for choosing which frames will or will not be themed.

Quote from chaud »

DeuceCommander gives me an error when mousing over the menu items, they do not open, and opening bagnon froze my wow client. Otherwise looks amazing, will reinstall after it has had time to mature.

Can I get the exact error when you mouseover? And is the freeze repeatable, as in, does it happen every time you open bagnon with it running?

Edit: Tested both, I neither get errors nor freezes with these addons; would love to have more details!

Quote from Kameril »

Quote from X-buZZ »

I have a little request: Would it be possible to add theme support fpr ArkInventory?

I'll look into supporting it tonight.

Sorry for the delay, but I looked into it and ArkInventory uses an incredible amount of children in its bag frames. Scaling or fading it destroys my fps: from 116 fps to single digits when I attempt to open it. So at this point I'm choosing not to support it.

Quote from chaud »

Quote from Kameril »

Can I get the exact error when you mouseover? And is the freeze repeatable, as in, does it happen every time you open bagnon with it running?

Edit: Tested both, I neither get errors nor freezes with these addons; would love to have more details!

2007/09/15 20:45:11-1-x21]: VisualThemes-r48755\AddOns\Dewdrop.lua:54: attempt to index field '?' (a nil value)
(tail call): ?:
Skinner-2.1\SkinMe\Dewdrop.lua:66: in function <Interface\AddOns\Skinner\SkinMe\Dewdrop.lua:61>
(tail call): ?:

---

Occurs when mousing over anything in the list, the menus don't show the items. Updated everything with WAU before opening WoW. Pretty much happens with anything on fubar that I try to right click. Just tried right clicking Click 2 Cast and WoW client froze. Don't want to log on to my main to check vbagnon again right now, but I'll get that for you soon. (Made a mistake in arenas today)

Thanks for more details, unfortunately I'm unable to reproduce this. I've looked through the code and the only way for this to happen is for another AddOn (that's neither Skinner nor VisualThemes) failing to properly pass arguments through their OnEnter hook. This could possibly be creating an infinite loop somewhere and causing the client to lockup. But, this is up to whichever AddOn that's breaking the hook to fix, there's nothing I can (or should) do in VT.

If you could try with only VT, Skinner, FuBar and DeuceCommander loaded and see if the error or lock up still occurs I'd appreciate it; so that I could confirm my speculation.

Still getting these errors even after the update that addressed this


(DewdropLib):790: Dewdrop20Button1:SetPoint(): Dewdrop20Level2 is dependent on this.