Recent changes changed the default # of players shown to 13 instead of 10 (making the window longer) which is annoying and I can't find an option to change it.
r329 build issues:
1. Same problem with window resizing - width of bars does not changing. Moreover - when i change some options (like font ot texture of bar's, etc) window width changed back - to previous value, but there is now no option to change it.
2. Reporting is ok now, but only by pressing new "Report" mini-button. When i select Report in menu - appears Report window with no buttons or texts and raises this error: //"Message: Interface\AddOns\Skada\Menus.lua:394: attempt to index local 'window' (a nil value)"//
3. Window button "Reset" does not work - even no highlighting when mouse ower. From menu it works as usually.
Actually you can decrease the number of bars/width etc by resizing the window. His frame changes are alpha so I am sure he will whip them into shape soon:)
Any reason why your Absorbs module records widely innacurate information in regards to Paladin bubbles via Illuminated Healing Mastery?
I'm seeing variances in numbers of over 1 million effective healing difference between your mod and World of Logs on my Pally.
In game the meters attribute the vast majority of the shields to me, and not my Pally healing partner. Yet on World of Logs its properly attributed to the right healer. You can tell because my total healing for spells that generate IH has a maximum limit of 13-15% of my total depending on my equipped Mastery Gear and in-game the percent sometimes exceeds 20-30%.
As was mentioned, there's either an extra frame appearing under the Skada window or the background/border settings are not saving or being applied correctly.
Also, InterfaceOptionsFrame_OpenToCategory("Category") doesn't work very well when a user has a lot of add-ons or the frame's hidden (not sure what causes it). In that case, any add-on that uses a string rather than frame causes it to just open to the default options panel (Game > Controls). At least that's the behavior I get.
If I change the instances where the string is called to:
Hi, yes I am getting 132 errors now with this addon in wow..
==============================================================================
World of WarCraft: Retail Build (build 14545)
Exe: C:\Program Files\World of Warcraft\WoW.exe
Time: Aug 31, 2011 3:19:05.062 AM
User: Lindz
Computer: LINDSEY
------------------------------------------------------------------------------
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: C:\Program Files\World of Warcraft\WoW.exe
ProcessID: 2024
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:0050523A
The instruction at "0x0050523A" referenced memory at "0x00000049".
The memory could not be "read".
WoWBuild: 14545
Version: 4.2.2
Type: WoW
Platform: X86
Realm: Argent Dawn (206.18.98.151:3724)
Local Zone: Stormwind City
Local Player: Carlaa, 020000000080DD58, (-8728.23,361.274,100.962)
Locked Target: Training Dummy, F130B637000012CF, (-8724.32,362.943,100.901)
Last Enemy Target: Training Dummy, F130B637000012CF, (-8724.32,362.943,100.901)
Total lua memory: 47314KB
Current Addon: Skada
Current Addon function: <unnamed>:SetPoint
Current Addon object: SkadaBarWindowSkada
Yeah, Blizz also tells you to run repair.exe and delete WTF and Interface folders whatever problem you run into...
most GMs just don't have a clue beyond what their knowledge base tells them (or just don't care to read/use them, as there's also an official support article stating several possible causes).
The error states, that a certain part of memory could not be read. And while Skada is triggering this, because you may just not need that part of memory without it, because of lower overall consumption, this most certainly is a driver or hardware problem.
Addons can cause error #132 and hard crash the client.
The error he posted is very telling.
It is just one of the possible causes but you shouldn't discount it offhandedly.
I know this for a fact because I have actually created that problem myself in one of my addons during development (never got published with that error until it was fixed)
It is rather obvious that the problem in this case is with an operation (not necessarily the :SetPoint() but most likely) on an unnamed frame.
Every time a popup dialog box is shown, the corresponding entry in StaticPopupDialogs is being recreated from scratch, with identical information each time. Not only is this wasting memory, but it makes it impossible to modify the entry table (say, to change the timeout).
The simplest change would to move the assignment of [FONT="Courier New"]StaticPopupDialogs["ResetSkadaDialog"][/FONT] out of the ask_for_reset() function, to just above it instead. Then ask_for_reset() becomes a simple one-liner.
edit: this has nothing to do with whatever error lin37 is seeing; consider it a separate thread.
Every time a popup dialog box is shown, the corresponding entry in StaticPopupDialogs is being recreated from scratch, with identical information each time. Not only is this wasting memory, but it makes it impossible to modify the entry table (say, to change the timeout).
The simplest change would to move the assignment of [FONT="Courier New"]StaticPopupDialogs["ResetSkadaDialog"][/FONT] out of the ask_for_reset() function, to just above it instead. Then ask_for_reset() becomes a simple one-liner.
edit: this has nothing to do with whatever error lin37 is seeing; consider it a separate thread.
also if one would add "preferredIndex = 3," to the SPD properties it would avoid the famous Glyph UI taint.
Skada has a really hard time with battle rezes under certain conditions. I don't know what those conditions are. I finally just deleted the Skada_Deaths folder after each update.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium1. Same problem with window resizing - width of bars does not changing. Moreover - when i change some options (like font ot texture of bar's, etc) window width changed back - to previous value, but there is now no option to change it.
2. Reporting is ok now, but only by pressing new "Report" mini-button. When i select Report in menu - appears Report window with no buttons or texts and raises this error: //"Message: Interface\AddOns\Skada\Menus.lua:394: attempt to index local 'window' (a nil value)"//
3. Window button "Reset" does not work - even no highlighting when mouse ower. From menu it works as usually.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAny reason why your Absorbs module records widely innacurate information in regards to Paladin bubbles via Illuminated Healing Mastery?
I'm seeing variances in numbers of over 1 million effective healing difference between your mod and World of Logs on my Pally.
In game the meters attribute the vast majority of the shields to me, and not my Pally healing partner. Yet on World of Logs its properly attributed to the right healer. You can tell because my total healing for spells that generate IH has a maximum limit of 13-15% of my total depending on my equipped Mastery Gear and in-game the percent sometimes exceeds 20-30%.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAlso, InterfaceOptionsFrame_OpenToCategory("Category") doesn't work very well when a user has a lot of add-ons or the frame's hidden (not sure what causes it). In that case, any add-on that uses a string rather than frame causes it to just open to the default options panel (Game > Controls). At least that's the behavior I get.
If I change the instances where the string is called to:
InterfaceOptionsFrame_OpenToCategory(self.profilesFrame) InterfaceOptionsFrame_OpenToCategory(self.optionsFrame)Then, not only does it open correctly to Skada, it also forces the group to be expanded already.Date: 2011-08-13 12:30:53
ID: -1
Error occured in: Global
Count: 1
Message: ..\AddOns\SkadaDamage\Damage.lua line 315:
attempt to index local 'player' (a nil value)
Debug:
[C]: ?
SkadaDamage\Damage.lua:315: Enter()
Skada\Skada.lua:1901: AddSubviewToTooltip()
Skada\BarDisplay.lua:145:
Skada\BarDisplay.lua:122
Skada\BarDisplay.lua:238:
Skada\BarDisplay.lua:238
==============================================================================
World of WarCraft: Retail Build (build 14545)
Exe: C:\Program Files\World of Warcraft\WoW.exe
Time: Aug 31, 2011 3:19:05.062 AM
User: Lindz
Computer: LINDSEY
------------------------------------------------------------------------------
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: C:\Program Files\World of Warcraft\WoW.exe
ProcessID: 2024
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:0050523A
The instruction at "0x0050523A" referenced memory at "0x00000049".
The memory could not be "read".
WoWBuild: 14545
Version: 4.2.2
Type: WoW
Platform: X86
Realm: Argent Dawn (206.18.98.151:3724)
Local Zone: Stormwind City
Local Player: Carlaa, 020000000080DD58, (-8728.23,361.274,100.962)
Locked Target: Training Dummy, F130B637000012CF, (-8724.32,362.943,100.901)
Last Enemy Target: Training Dummy, F130B637000012CF, (-8724.32,362.943,100.901)
Total lua memory: 47314KB
Current Addon: Skada
Current Addon function: <unnamed>:SetPoint
Current Addon object: SkadaBarWindowSkada
there's a complete listing of steps to do and updating video drivers is just one of the solutions
most GMs just don't have a clue beyond what their knowledge base tells them (or just don't care to read/use them, as there's also an official support article stating several possible causes).
The error states, that a certain part of memory could not be read. And while Skada is triggering this, because you may just not need that part of memory without it, because of lower overall consumption, this most certainly is a driver or hardware problem.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe error he posted is very telling.
It is just one of the possible causes but you shouldn't discount it offhandedly.
I know this for a fact because I have actually created that problem myself in one of my addons during development (never got published with that error until it was fixed)
It is rather obvious that the problem in this case is with an operation (not necessarily the :SetPoint() but most likely) on an unnamed frame.
File a ticket with Skada if you haven't already.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe simplest change would to move the assignment of [FONT="Courier New"]StaticPopupDialogs["ResetSkadaDialog"][/FONT] out of the ask_for_reset() function, to just above it instead. Then ask_for_reset() becomes a simple one-liner.
edit: this has nothing to do with whatever error lin37 is seeing; consider it a separate thread.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderatoralso if one would add "preferredIndex = 3," to the SPD properties it would avoid the famous Glyph UI taint.
Date: 2011-10-13 15:54:50
ID: 1
Error occured in: Global
Count: 6
Message: ..\AddOns\SkadaDeaths\Deaths.lua line 98:
attempt to concatenate a nil value
Debug:
(tail call): ?
(tail call): ?
SkadaDeaths\Deaths.lua:98: func()
Skada\Skada.lua:1402:
Skada\Skada.lua:1302
[string "safecall Dispatcher[19]"]:4:
[string "safecall Dispatcher[19]"]:4
[C]: ?
[string "safecall Dispatcher[19]"]:13: ?()
...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...ace\AddOns\TomTom\libs\AceEvent-3.0\AceEvent-3.0.lua:120:
...ace\AddOns\TomTom\libs\AceEvent-3.0\AceEvent-3.0.lua:119
-
View User Profile
-
View Posts
-
Send Message
Curse Premium*bump*