DMF Quest

DMF Quest

42.9k Downloads

InterfaceOptionsFrame nil value error

nancikennedy opened this issue ยท 2 comments

commented

In testing the for the previously reported bug, I happened to move the DMFQ window on screen and got the error below. It happens every time the window is moved by dragging it. Using the sliders in the options to change its on-screen position did not trigger this. In both cases, the error did not affect the actual saving of the window's new position.

1x Interface/AddOns/DMFQuest/DMFQuest.lua:214: attempt to index global 'InterfaceOptionsFrame' (a nil value)
[string "@Interface/AddOns/DMFQuest/DMFQuest.lua"]:214: in function <Interface/AddOns/DMFQuest/DMFQuest.lua:203>

Locals:
self = Frame {
0 =
}
button = "LeftButton"
x = 63.083202
y = 403.999908
(*temporary) = nil
(*temporary) = nil
(*temporary) = "BOTTOMLEFT"
(*temporary) = 63.083202
(*temporary) = 403.999908
(*temporary) = "attempt to index global 'InterfaceOptionsFrame' (a nil value)"
f = DMFQuestFrame {
0 =
CheckDMF = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:269
CheckPortalZone = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:345
Buttons =

{
}
Print = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:129
Lines =
{
}
UpdateProfession = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:644
GetItemName = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:1013
UpdateItems = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:517
BuyItems = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:940
title = FontString {
}
UpdateQuests = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:737
CheckDB = defined @Interface/AddOns/DMFQuest/DMFQuest.lua:256
Strings =
{
}
}
db =
{
HideMax = false
DeathMetalKnight = true
ShowItemRewards = true
FadedTreasureMap = true
items =
{
}
TestYourStrength = true
AutoBuy = true
YPos = 403.999908
PetBattle = true
UseTimeOffset = true
HideLow = false
XPos = 63.083202
}
panel = DMFQuestOptions {
0 =
name = "DMFQuest"
}

commented

There is always something I forget to test...

commented

Version 2.2.1 should fix this and also the unreported issue of /dmfq config causing same error on different line.