In-game config panel (breaks on Shared function)

[Lyelu]

Hi,
I'm adding in a config panel on an oUF layout, and I'm getting stuck because one function will not accept the values from the DB. All the other functions will accept it, but this one makes the entire layout disappear on reload (not loading anything, I think.) I am using Nivea's file to start, because it had all the power bars I wanted. I'm first adding an Ace config and then I will start destroying the layout.

Here's the (shortened) function that will not accept values from my Ace DB. Every other function in the file has no issues:

local Shared = function(self, unit, isSingle)
	local playerClass = select(2, UnitClass("player"))	
	local unitIsPartyPet = self:GetAttribute("unitsuffix") == "pet"
	self.menu = menu
	self:SetScript("OnEnter", UnitFrame_OnEnter)
	self:SetScript("OnLeave", UnitFrame_OnLeave)
	self:RegisterForClicks"AnyDown"
	
	-- malfunctions here on db value
	if Henna.db.profile.HideBlizzardAuras then
		local BlizzFrame = _G['BuffFrame']
		BlizzFrame:UnregisterEvent('UNIT_AURA')
		BlizzFrame:Hide()
		BlizzFrame = _G['TemporaryEnchantFrame']
		BlizzFrame:Hide()
	end
	
	-- malfunctions here on db value
	local hp = CreateFrame("StatusBar", nil, self)
	hp:SetHeight(Henna.db.profile.heightHP)	
	hp:SetStatusBarTexture(Henna.db.profile.HPtex)
	hp:SetPoint"TOP"
	hp:SetPoint"LEFT"
	hp:SetPoint"RIGHT"
	hp:SetStatusBarColor(unpack(Henna.db.profile.maincolor))
	hp:GetStatusBarTexture():SetHorizTile(true)
	
	hp.frequentUpdates = true
	self.Health = hp
	self.Health.PostUpdate = PostUpdateHealth	
end

This function is referenced later, throughout the file:

local UnitSpecific = {
	player = function(self, ...)
		Shared(self, ...)
		  -- no issue here with db value
		if Henna.db.profile.useCastbar then	
			createCastbar(self)	
		end
	-- etc etc
	end,			
}

oUF:RegisterStyle("Henna", Shared)

Is there something about the Shared function that causes it to break whenever I put in values from DB?
Thanks.

[yj589794]

I suspect a scope issue could be the cause, but without seeing all your code it is difficult to say for certain.

[Lyelu]

Here's a paste of the entire file.
http://paste.wowace.com/2881/

Values called cfg are from Nivea's original code. Values called Henna.db.profile are my code.

I have simple things working, like the color picker, but most of my options file right now is just defaults, like so:

local addon, ns = ...

defaults = {
	profile = {
	maincolor = { r = 0, g = .5, b = 1, a = .5 },
        -- lots more values, this is shortened
	},
}

[Phanx]

Install BugSack. I strongly suspect that you'll see some "attempt to index ____ (a nil value)" errors, caused by the fact that when you're spawning your frames, Henna.db has not yet been defined. Try moving your :Spawn calls (basically, everything that's currently inside your oUF:Factory call) into your Henna:OnInitialize() function, after you define the db.

[Lyelu]

It does indeed say that. Seems like I have quite a few fights with this "nil value". It's like a bad rogue... constantly following you around trying to Backstab you from the front.

Anyway, so far, the file objects when I move anything around, so perhaps I should start over. Is there an existing oUF layout that uses Ace Config?

[Dawn]

Originally Posted by Lyelu It does indeed say that. Seems like I have quite a few fights with this "nil value". It's like a bad rogue... constantly following you around trying to Backstab you from the front. Anyway, so far, the file objects when I move anything around, so perhaps I should start over. Is there an existing oUF layout that uses Ace Config?

Not on this site, afaik. You could take a look at oUF_Nivaya. It has a working config for quite some time, Ace free.

E: Another layout with in game config is oUF Lure.

[Lyelu]

Thanks Dawn. I'd read Nivaya several times, and it was too hard for me, but I think Lure is a great place for me to start. It appears to be written in a way easier for a beginner.

[lurelure]

Originally Posted by Lyelu Thanks Dawn. I'd read Nivaya several times, and it was too hard for me, but I think Lure is a great place for me to start. It appears to be written in a way easier for a beginner.

Probably because it's written by a beginner...
I've rewritten it lots of times, and its far from perfect, but i'm quite happy with where it's at now.

[Phanx]

oUF_Phanx also has an in-game config panel, and does not use any Ace3 or other big libraries. (It does use a few "libraries" but they're only libraries because it was the most convenient way for me to share my custom config widget code between my addons.)

But, what you have right now should work, if you do what I suggested in my last post:

Originally Posted by Phanx Try moving your :Spawn calls (basically, everything that's currently inside your oUF:Factory call) into your Henna:OnInitialize() function, after you define the db.

[Luzzifus]

Originally Posted by lurelure Probably because it's written by a beginner... I've rewritten it lots of times, and its far from perfect, but i'm quite happy with where it's at now.

I just wanted to answer something semi-nice, but after reading your comment the third or fourth time I realized who you were referring to.

Well, even if you would have referred to me, you would have been at least partially correct. It was basically my first contact with lua and I started off by copying the structure from another layout. I know that my code is not easy to read, and I'm really not proud of many parts. If I'd decide to completely rewrite oUF_Nivaya (which I probably never will do), I'd do many things differently.

PS: oUF_Nivaya does use AceConfig.

[Dawn]

Originally Posted by Luzzifus PS: oUF_Nivaya does use AceConfig.

Oh, didn't know that. I haven't looked at your code, yet. I stand corrected.

[Lyelu]

Well I finally got some basics working... Nivaya's code wasn't possible for me to imitate because it just uses more things than I know yet. But having read all of yours several times, I have finally managed to get a health statusbar up on the screen. I had quite a time with the loading orders etc.

Edit: Deleted a question here, because I found a workaround.