calling variables accorss modules accross files

Grimsin · 01-23-10, 01:17 PM

confused yet? i am

okay so heres the deal... in one file it creates the variable based on what resolution is set. it only does this once per first use of the UI, now then another file uses that variable to chose layouts. well for some reason the other file cant pick out the variables. also the addon = {} is also in another file... is that maybe the problem? do i need to make the variables global somehow? the file that is supposed to find the variables for the layouts lil chunk to do so looks like this,

lua Code:

local GPartyMainEvents = CreateFrame("Frame", nil, UIParent)
GPartyMainEvents:RegisterEvent("VARIABLES_LOADED")
 
 
GrimUI.GPartyMainEvents = GPartyMainEvents
 
GPartyMainEvents:SetScript("OnEvent", function(self)
    
    if GrimUIData.GrimResolution == "1" then
        GrimLayout1()       
    elseif GrimUIData.GrimResolution == "2" then 
        GrimLayout2()
    else
        GrimLayout1()
    end
    
 
end)

Xus · 01-23-10, 01:36 PM

by the looks of it GrimUIData should indeed be global (simply don't put local in front of it when you first make it hah. Or move it to a table that you already made global). Also make sure that you the resolution is already checked before the variables event!

cloudwolf · 01-23-10, 01:59 PM

a local variable is only good for the functoin that its in. So think of each file a as a function.
say random.lua

Code:

local myvar="hi"
function dostuff()
print(myvar) -- it will output hi
local myothervar="hi"
print(myothervar)-- it will also output hi
end
print(myvar) -- it will print hi
print(myothervar) -- this will be nil.

now lets say you have another lua file
other.lua

Code:

print(myvar) -- this will be nil

the reason its nil is because myvar is only real for random.lua

Akryn · 01-23-10, 02:05 PM

Rather than make a global, at the top of each file you can add:

Code:

local _, myNamespace = ...

And then use the myNamespace (or whatever you want to call it) table for storing variables that you want to have addon-wide scope:

Code:

myNamespace.x = "hello"
myNamespace.y = 234

Grimsin · 01-23-10, 02:54 PM

well i have this at the top of the core file

GrimUI = {}
local mt_grimui = {__index = GrimUI}
local modules = {}
local defaults = {__index={}}
local dummy = function() end
GrimUI.Modules = modules
GrimUI.Dummy = dummy

function GrimUI:RegisterModule(name)
local module = setmetatable({}, mt_grimui)
modules[name] = module
return module
end

with this at the top of the module files

local module = GrimUI:RegisterModule("ExpRepBar")

it was my understanding that it made all my functions work within one another

Grimsin · 01-23-10, 07:42 PM

my real problem was that i was under the impression player_login fired before addon_loaded

all better now.