Can't load other lua file

[Platine]

Hello,
I have a simple structure:

MyAddon.toc file:

## Interface: 60200
## Title: MyAddon
## Notes: Description of MyAddon
other_file.lua
MyAddon.lua

other_file.lua :

print ("Text from other_file.lua");

MyAddon.lua :

print ("Text from MyAddon.lua");

and finally I have received text on wow console:

Text from MyAddon.lua

Where is text from the first file (other_file.lua).
It isn't execute?

[myrroddin]

You need to use the vaarg to do this. That is shorthand for "variable argument" and looks like this in code:

-- other_file.lua
local AddOn, pt = ... -- string, cross-file table, ... is the vaarg
print(AddOn)
-- >> MyAddon (from the ToC's Title line)
 
pt.otherText = "Text from other_file.lua"
print(pt.MyAddonText)
-- >> "Text from MyAddon.lua"
 
-- MyAddon.lua
local AddOn, pt = ...
pt.MyAddonText = "Text from MyAddon.lua"
print(pt.otherText)
-- >> "Text from other_file.lua"

You can also do cross-file function calls using the table.

-- file #1
local titleName, myTable = ... -- remember both are variables, and can be called whatever you wish
 
function myTable:PrintText(textString)
    print(textString)
end
 
-- file #2
local Bob, Nancy = ... -- lack of consistancy, but doesn't matter what we name them
 
local myString = "We should call the vaargs the same in all files for readability"
 
Nancy:PrintText(myString)
-- >> We should call the vaargs the same in all files for readability

[myrroddin]

Also, remember that the order of your Lua files in your Toc matters. For example, in one of my AddOns, I have a core or main file, and the options you'd see in the Interface .. AddOns list comes from a second file. You don't need to do this, but it was my way of making things easier to debug with a large AddOn.

-- ToC
## all other stuff as expected
main.lua
options.lua
 
-- main.lua
-- register events, done ADDON_LOADED, etc
local addon_name, pt = ...
function pt:ADDON_LOADED(...)
    if ... ~= addon_name then
        return -- not my AddOn
    end
 
   pt.options = self:MyOptions() -- see options.lua
end
 
-- options.lua
local addon_name, pt = ...
function pt:MyOptions()
    local options = {
        -- checkboxes, sliders, inputs, etc
    }
    return options -- populate pt.options
end

[Lombra]

If you successfully included all of your code here, then it's probably just a matter of restarting the client, which you need to do whenever new file names are added.

[SDPhantom]

Originally Posted by Lombra If you successfully included all of your code here, then it's probably just a matter of restarting the client, which you need to do whenever new file names are added.

Expanding on this, ToC file changes apply after you back out to the login screen. Adding files to the addon folders only get picked up after a full client restart.

[Seerah]

I don't think he was wanting to print out something from the other Lua file, but something from THAT Lua file.

Sometimes print statements in the main chunk of a file don't print if the code is executed before the chat frame loads.

[SDPhantom]

Originally Posted by Seerah Sometimes print statements in the main chunk of a file don't print if the code is executed before the chat frame loads.

In all honesty, I've called print() from the main chunk many times in testing and haven't had it fail once.

[Platine]

It is interesting.
I have made the structure of MyAddon for new, and all work properly:

MyAddon.toc

## Interface: 60200
## Title: MyAddon
## Author: Platine
## Version: v60200-1.0

File1.lua
MyAddon.lua
File2.lua

File1.lua

print ("Text from File1.lua");

MyAddon.lua

print ("Text from MyAddon.lua");

File2.lua

print ("Text from File2.lua");

Chat frame on Wow

Text from File1.lua
Text from MyAddon.lua
Text from File2.lua

It was need a full restart of Client.

[Seerah]

Another culprit is that some chat frame addons will clear the chat window (when changing the max number of lines displayed, for example).