r20160419095257
Details
-
FilenameOakInterruptsDisplay-r20160419095257.zip
-
Uploaded by
-
UploadedApr 19, 2016
-
Size21.83 KB
-
Downloads68
-
MD5081558ed8ac7bebf5ea9754ea2fe6e45
Supported WoW Retail Versions
- 6.2.4
Changelog
Oakshlaran:
- Disabled nolib creation
- Add saving of display settings
Previously, users would have to set up any displays everytime their UI
reloaded. This change has added the CharDisplays variable to save
settings between sessions. Currently saved settings are:
- position of a display
- rotation/announce flag
- locked flag
- grow direction
- autoinclude flag
When the user logs in displays are now created to replicate the
situation at the previous logout (though the lists are not populated),
with the one small caveat that the display's name (as returned by
GetName(), not the user chosen name) of the display may have changed.
Because of this the position settings are not saved via SetUserPlaced,
but are instead included in CharDisplays.
In addition some functions were moved and renamed in an effort to bring
a little more consistency to the structure of the code.
Known issues:
- If the user reloads during combat and drops combat while
reloading, a call to BGColor* can occur for a nil frame
issue: www.wowace.com/addons/oakinterruptsdisplay/tickets/1-save-display-list-settings/
- Add show/hide slash commands
Previously there was no way to hide a display, the user would have to
delete it and then recreate when it was needed again (so you would just
never hide it). To address this two new display interface functions were
added and slash commands calling them included. Additionally the
functions to create and close displays were renamed for consistency.
issue: www.wowace.com/addons/oakinterruptsdisplay/tickets/3-show-hide-list/
- Fix background when changing display direction
- Add background colouring functions; fix highlight bug
Previously when in combat, if a rotation list was edited (someone was
removed or the order rearranged) the highlighting of frames did not
update properly. Observed bugs were:
- if the next interrupter was removed, when that frame was reused by
the FramePool, it would still be highlighted
- if the order was rearranged incombat, the highlighting would not
update to reflect this
- when leaving combat, if the highlighting was desynced from the
rotation it would not unhighlight everything
To fix these issues general use background colouring functions were
added to display.lua intended to be used for all highlighting puposes.
The colouring of new interrupter frames was moved out of InitFrame (as
this function only fires when a new frame is created, not when reused)
fixing the issue of reused frames being highlighted and colouring of a
list is now done after rearrange.MouseUpdate which is when the
rearrangement of the order takes place.
- Fix rotation not updating properly when on cooldown
- Fixed bug occuring when 'polling' data field changes.
- Fixed bug introduced when updating dataobject spec to include 'polling'
- Rotation logic and lock/unlock combat flag bump.
- rotation now skips a player is they're disconnected
- lock/unlock combat flag is now case insensitive
- The combat flag for lock/unlock is now case insensitive.
- Bug fixes.
- Fixed interrupt rotation logic bug always jumping to person after
whoever used an interrupt
- Fixed bug when removing interrupter from a list
- Rearranged library inclusions; added .pkgmeta.
- Initial comming.