Closed ghost closed 6 years ago
I could add an option to specify a table key to use within an existing table. It wouldn't be completely merged like you wanted, but it would be in one parent table.
Something like this: Wasabi:New(name, 'KkthnxUIData', 'General', defaults)
KkthnxUIData = {
["General"] = {
["AutoScale"] = true,
["FontSize"] = 13,
},
["ActionBars"] = {
["BarsLocked"] = true,
},
}
Another alternative is simply allowing no savedvariable passed to sub-frames, let them leech off the main one. I'll see what I'll do.
Also, next version will have profile management, so yo won't need to implement that yourself.
You simply rock! Looking forward to the profile management. Thank you for the info.
This one is sadly delayed as I can't really find a good way to implement this. Profiles are still being considered though, but sub-tables sadly won't be.
Superseded by #1.
This is just a reminder for the Database rework.
https://www.wowinterface.com/downloads/info24061-Wasabi.html#comments From the link above you can see my examples.
Hey, p3lim. Once again thank you for your work.
Currently, I noticed you have to use a Database for each module you make. The below example should explain more.
So, in theory, I am wondering something here. I am wanting to just use one SavedVariable for everything. I just want to use KkthnxUIDB instead of filling ActionBarDB, GeneralDB, NameplatesDB and so on. Now I could have overlooked this as I am still checking out your Lib.
To kinda show what I am wanting is more of a compact Database from your config. Would be a lot cleaner.