PvPLog 3.2.0 is attached.

2010-10-16 * 3.2.0
* Replaced MyMinimapButton.lua with a simpler (for me) implementation.
* Added "/pl radius" to display the radius of the minimap button.
* Added "/pl radius <value>" to change the radius of the minimap button.
* Added "/pl position" to display the position of the minimap button.
* Added "/pl position <value>" to change the position of the minimap button.

2010-10-10 * 3.1.1
* Changed TOC to 40000
* Changes for WoW 4.0.1

This version has not had extensive testing under 4.0.1 (one death) so let me know if there are any problems. I had trouble getting MyMinimapButton to work under 4.0.1 so I replaced it with something simpler. It is still in the zip and may come back later.

Hey bsmorgan,

Im getting an error with PVP log. I tried uninstalling and reinstalling and also clearing all my .lua files.

The initial error I get is:

Message: ..\AddOns\PvPLog\PvPLogButton.lua line 21:
attempt to index field '?' (a nil value)
Debug:
(tail call): ?
[C]: ?
PvPLog\PvPLogButton.lua:21: PvPLogButton_Init()
[string "*:OnEvent"]:1:
[string "*:OnEvent"]:1


If I try loading without any addons besides PVPLog I get this error:

Message: [string "compat.lua"]:21: bad argument #1 to 'rad' (number expected, got nil)
Time: 11/28/10 23:16:37
Count: 1
Stack: [C]: in function `rad'
[string "compat.lua"]:21: in function `cos'
Interface\AddOns\PvPLog\PvPLogButton.lua:53: in function `PvPLogButton_UpdatePosition'
[string "*:OnEvent"]:2: in function <[string "*:OnEvent"]:1>

Locals: (*temporary) = nil
(*temporary) = "number expected, got nil"

Any ideas?? Thanks in advance!

The only thing I can think of is that you are not using the enUS WoW client. Could you please post your debug logs (see the sticky for how to create these).

Regards,

Brad

I'm guessing again but I think the PvPLogButton "VARIABLES_LOADED" event is firing before the PvpLog "VARIABLES_LOADED" event. I'll have to figure out how to make that NOT happen. I'd still like to see your debug stuff.

Regards,

Brad

I thought VARIABLES_LOADED was removed from consideration in the addon process.

Until 3.0, VARIABLES_LOADED used to fire upon completion of the addon loading process; since 3.0, it is fired in response to CVars, Keybindings and other associated "Blizzard" variables being loaded, and may therefore be delayed until after PLAYER_ENTERING_WORLD. The event may still be useful to override positioning data stored in layout-cache.txt

I think PLAYER_LOGIN is now the preferred event.


Information from http://www.wowwiki.com/AddOn_loading_process