Upgraded from the last one before major code changes took place (r63066, Feb. 27/08, still works fine) to the latest (r70835, Apr. 22/08). Updated standalone libraries, USEng client/server, WoW 2.4.1 live.
It bugs out at log on and fails to load (the bar does not appear). The following errors occur at the same time at logon: Xparky-2.0\\Bar.lua:688: '}' expected (to close '{' at line 684) near 'arg'
and Xparky-2.0\\Xparky.lua:143: bad argument #1 to 'ipairs' (table expected, got nil)\nXparky-2.0\\Xparky.lua:143: in function `GenerateBars'\nXparky-2.0\\Xparky.lua:126: in function <Interface\\AddOns\\Xparky\\Xparky.lua:101>\n(tail call): ?:\n<in C code>: ?\n<string>:\"safecall Dispatcher[1]\":9: in function <[string \"safecall Dispatcher[1]\"]:5>\n(tail call): ?:\nAceAddon-3.0\\AceAddon-3.0.lua:316: in function `InitializeAddon'\nAceAddon-3.0\\AceAddon-3.0.lua:404: in function <Interface\\AddOns\\Ace3\\AceAddon-3.0\\AceAddon-3.0.lua:397>
Revert back to r63066 and Xparky works properly again.
I've pretty much stopped playing WoW due to a combination of an unfortunate formatting incident and a general burnout/disillusionment about the game, so development may be sparse if at all existent.
Current state of affairs is that you can create/delete bars, reposition, link to frames. They still need to be hooked up properly to events and honour bars need fiddling with. Anyone who wishes to take over development should feel free =)
Sorry folks, but unless WotLK really blows my socks off, I'm not going to be playing WoW for a good while.
hi Wobin, could you tag this current development version, and revert the trunk to 63122 (i beleive that was the last stable revision) as that was in good working order but just needs some event tweaking (like update on combat ended)
Judging from his last post, you could probably tag the last stable version and fix trunk. ;) (basically the opposite of what you were asking, but meh. ;p)
well, i dont rly want to pick up the pieces :D havent even looked at the current code tbh, but i dont have the time right now to work through it anyway.
It bugs out at log on and fails to load (the bar does not appear). The following errors occur at the same time at logon:
Xparky-2.0\\Bar.lua:688: '}' expected (to close '{' at line 684) near 'arg'
and
Xparky-2.0\\Xparky.lua:143: bad argument #1 to 'ipairs' (table expected, got nil)\nXparky-2.0\\Xparky.lua:143: in function `GenerateBars'\nXparky-2.0\\Xparky.lua:126: in function <Interface\\AddOns\\Xparky\\Xparky.lua:101>\n(tail call): ?:\n<in C code>: ?\n<string>:\"safecall Dispatcher[1]\":9: in function <[string \"safecall Dispatcher[1]\"]:5>\n(tail call): ?:\nAceAddon-3.0\\AceAddon-3.0.lua:316: in function `InitializeAddon'\nAceAddon-3.0\\AceAddon-3.0.lua:404: in function <Interface\\AddOns\\Ace3\\AceAddon-3.0\\AceAddon-3.0.lua:397>
Revert back to r63066 and Xparky works properly again.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumCurrent state of affairs is that you can create/delete bars, reposition, link to frames. They still need to be hooked up properly to events and honour bars need fiddling with. Anyone who wishes to take over development should feel free =)
Sorry folks, but unless WotLK really blows my socks off, I'm not going to be playing WoW for a good while.
Cheers!
Oridan
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumDid that, latest stable version does the job anyway :)
Interface\AddOns\Xparky\Bar.lua:688: '}' expected (to close '{' at line 684) near 'arg'
Interface\AddOns\Xparky\Xparky.lua:145: attempt to index global 'XparkyBar' (a nil value)
I guess i have to try the WoWI version too.
I just use FuXPFu. Less clutter and easier to use ;)