It should have a full valid URL there for you to use. If you're actually seeing [email protected] there, maybe you have some browser addon or other tool that somehow mangles the URL and replace it with this token?
A better option would be to remove the SetPoint right there instead of clearing the points later. And I commited a change to do just that just now.
I do wonder though, this problem seems to only occur if you create the widget but then don't do anything with it. Even if I just create it and then add it to a hidden and otherwise untouched container, it never shows up, because the container takes over its handling.
So this means that any addon using it through AceConfigDialog didn't seem to ever trip into this problem. Not that I've noticed either way.
Ace3 does no such thing. The AceDB code handling profiles is quite simple and proven, the only time it touches profiles of characters other then the one you are currently on is when you delete a profile (it switches everyone that uses it to the default profile), otherwise it only ever touches the profile entry for your current character.
Note that SVs getting re-ordered is normal and just how Blizzard saves them.
AceGUI frames or widgets are not meant to be "normal" frames, you access them through the AceGUI API, not anything else.
If you want a frame in full control, create your own and either implement the AceGUI container API, or just shove a invisible "SimpleGroup" into it to serve as your main container, or a ScrollFrame container if you need scrolling.
Damage Meters do not need to be updated for class balancing changes. Different damage meters have always reported slightly different results based on different approaches in calculating DPS.
If you want an entirely accurate view, create a combat log and analyze it afterwards with warcraftlogs or similar websites.
Depending on your class, its expected that Bar 1 mirrors some other bar, since that is controlled by which stance you are in. Its all configurable in Bartender however.
Any other bars do not come with such a pre-defined config, so if Bar 3 matches Bar 8, you did some configuration to make it so.
That also shouldn't work. You are not allowed to overwrite the tables directly in self.db, as these are the special root tables and hold a bit of magic.
If you want to exchange the entire contents of the self.db.char table (or any self.db.* table), you need to delete its contents manually and then merge the existing table in.
The reason for this is that "self.db" itself is not actually something that is persisted in the SV. It just holds references to the individual tables which are persisted in the SV (with appropriate redirections for the context-sensitive storage areas) - if you overwrite that reference, then its no longer saved.
0
0
0
0
0
I do wonder though, this problem seems to only occur if you create the widget but then don't do anything with it. Even if I just create it and then add it to a hidden and otherwise untouched container, it never shows up, because the container takes over its handling.
So this means that any addon using it through AceConfigDialog didn't seem to ever trip into this problem. Not that I've noticed either way.
0
Note that SVs getting re-ordered is normal and just how Blizzard saves them.
0
0
0
If you want a frame in full control, create your own and either implement the AceGUI container API, or just shove a invisible "SimpleGroup" into it to serve as your main container, or a ScrollFrame container if you need scrolling.
0
0
0
If you want an entirely accurate view, create a combat log and analyze it afterwards with warcraftlogs or similar websites.
0
I've merged your posts into this thread.
0
Any other bars do not come with such a pre-defined config, so if Bar 3 matches Bar 8, you did some configuration to make it so.
0
If you want to exchange the entire contents of the self.db.char table (or any self.db.* table), you need to delete its contents manually and then merge the existing table in.
The reason for this is that "self.db" itself is not actually something that is persisted in the SV. It just holds references to the individual tables which are persisted in the SV (with appropriate redirections for the context-sensitive storage areas) - if you overwrite that reference, then its no longer saved.