View Single Post
10-30-23, 12:04 PM   #3
myrroddin
A Pyroguard Emberseer
 
myrroddin's Avatar
AddOn Author - Click to view addons
Join Date: Oct 2008
Posts: 1,240
I have tried every idea that I can think of, and am still stuck. I am getting the following error, which I cannot decipher.
Lua Code:
  1. 2x ...nfig-3.0/AceConfigDialog-3.0-86/AceConfigDialog-3.0.lua:1854: AceConfigRegistry-3.0-21:ValidateOptionsTable(): SmartRes2.args.modules.Chat: unknown parameter
  2. [string "=[C]"]: ?
  3. [string "@Ace3/AceConfig-3.0-3/AceConfigRegistry-3.0-21/AceConfigRegistry-3.0.lua"]:50: in function <...-3.0/AceConfigRegistry-3.0/AceConfigRegistry-3.0.lua:45>
  4. [string "@Ace3/AceConfig-3.0-3/AceConfigRegistry-3.0-21/AceConfigRegistry-3.0.lua"]:239: in function <...-3.0/AceConfigRegistry-3.0/AceConfigRegistry-3.0.lua:220>
  5. [string "@Ace3/AceConfig-3.0-3/AceConfigRegistry-3.0-21/AceConfigRegistry-3.0.lua"]:255: in function <...-3.0/AceConfigRegistry-3.0/AceConfigRegistry-3.0.lua:220>
  6. [string "@Ace3/AceConfig-3.0-3/AceConfigRegistry-3.0-21/AceConfigRegistry-3.0.lua"]:283: in function `ValidateOptionsTable'
  7. [string "@Ace3/AceConfig-3.0-3/AceConfigRegistry-3.0-21/AceConfigRegistry-3.0.lua"]:325: in function `app'
  8. [string "@Ace3/AceConfig-3.0-3/AceConfigDialog-3.0-86/AceConfigDialog-3.0.lua"]:1854: in function `Open'
  9. [string "@SmartRes2/Core.lua"]:74: in function <SmartRes2/Core.lua:70>
  10. [string "@SmartRes2/Core.lua"]:134: in function <SmartRes2/Core.lua:128>
  11. [string "@Titan/TitanLDB.lua"]:298: in function <Titan/TitanLDB.lua:296>
  12.  
  13. Locals:
  14. (*temporary) = "AceConfigRegistry-3.0:ValidateOptionsTable(): SmartRes2.args.modules.Chat: unknown parameter"
My latest code push is on GitHub: https://github.com/Myrroddin/smartres2 I figure it is easier to read there than to download a zip.

Besides the error, some things do not make sense to me. I have looked at Skada and its modules for inspiration, yet things are going sideways.
  • How are the namespace and options table tied together, at least for a module?
  • Is my method to add the module options to the main options correct?
  • Will I be forced to make the module its own addon with its own SVs?
  • Am I referencing addon.db correctly in the module to set options? IE: the db shorthand?
  • Does resetting the profile also reset the module's options back to its defaults?
  • Why does a namespace need a profile table if namespaces cannot control their own profiles? IE: moduleDefaults.profile.enabled instead of simply moduleDefaults.enabled?

Last edited by myrroddin : 10-30-23 at 12:07 PM. Reason: Clarify a question
  Reply With Quote