Updating from 1.5.16 (4.3) to 1.6.5 (5.3)
I just came back from a bit of a break and I'm trying to get my layout up to date.
Could anyone give me a quick run-through of what has changed from 1.5.16 to 1.6.5? Currently I'm not getting and Lua errors - my frames are simply not being displayed. Thanks so much to anyone with a little time to help me get back into it! |
I'm wearing a t-shirt right now. Could you tell me what color it is?
Apart from that: https://github.com/haste/oUF/compare/1.5.16...1.6.5 http://www.wowinterface.com/download...html#changelog |
Yeah... sorry about that vagueness of my request. The GitHub comparison page is very helpful - thank you. I'll be more specific if I need something in the future.
|
Hey I fixed it! Just had to change a couple Tag functions.
|
I did the same thing - updating from 1.5.16 to 1.6.5.
Getting atm these errors: 1. Code:
1x oUF_Fauli-1.0\tags.lua:54: attempt to index field "TagEvents" (a nil value) Code:
1x oUF_Fauli-1.0\core.lua:124: Attempted to use invalid tag [fauli:hp]. if anyone wants to look through it: http://www.wowinterface.com/download...ouf_Fauli.html it's not that much of Code. |
okay, I got rid of these errors - and changed 2 against 1 error:
Code:
2x oUF_Fauli-1.0\core.lua:377: Bad argument #3 to "RegisterStyle" (function, table expected, got nil edit: thats my register style part: Code:
oUF:RegisterStyle("fauli", UnitStyle) |
If I read this right it would mean that either UnitStyle or BossStyle are not present when calling RegisterStyle.
|
Nah, it's even worse - I forgot to edit everything else (tags.lua, core.lua) to suit 1.6.5 - too much work just to update a still working layout.
Seem's i'll stuck with 1.5.16 until it won'T work anymore |
Quote:
If you're not using BugSack already, go install it now. The game's built-in error display can't show you errors that happen during the initial loading sequence, which is when the majority of errors you will encounter as an addon developer happen, making it pretty much useless for developers. Error messages will generally tell you exactly what's wrong on which line in which file, making it trivial to pinpoint the problem. Without error messages, you're pretty much working blind. |
although it's an ancient version, it doesn't throw any errors - as long, as I'm not trying to update the layout code to 1.6 ;)
Maybe I'm trying to code it again this weekend, then I'll gladly ask for your help :) |
All times are GMT -6. The time now is 10:23 PM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI