2.1.0.5-3-g7c00212
Details
-
FilenameWeakAuras-2.1.0.5-3-g7c00212.zip
-
Uploaded by
-
UploadedJul 6, 2015
-
Size3.19 MB
-
Downloads193
-
MD5ba8080a5c248471cedbf46a602b4c5b8
Supported WoW Retail Versions
- 6.2.0
Changelog
Infus:
- Rewrite import to use a dynFrame
- Try to fix corrupted entries
Since I know the root cause now, I'm pretty sure that data.id is the
one that is to be not trusted.
- Prevent users from corrupting their settings
So I was always baffled on how users could end up with a corrupted entry,
where db.displays[id].id was different from id.
What is happening is this:
- We decompress the data for a aura.
- This table gets added to db.displays db.displays[data.id] = data;
- The script is interrupted, so the import window is never hidden
- The user clicks on import again
- This detects that data.id is already existing so it changes data.id
- This actually also changes the data.id of the table already added
to db.displays
- Prevent that by hiding the import window first
