Mercurial > wow > ouroloot
comparison verbage.lua @ 116:fc2ff128835a
- Reset the 'clean' markers on all default-function option toggles.
- Fix a long-standing FIXME: Move all lib-scrollingtable and other
"display-only" data out of g_loot entries and into their own subclass-
style table; feed that to ST's SetData instead. No more 'cols'.
author | Farmbuyer of US-Kilrogg <farmbuyer@gmail.com> |
---|---|
date | Thu, 16 Aug 2012 17:11:57 -0400 |
parents | ce45011fab4c |
children | dbdab3780757 |
comparison
equal
deleted
inserted
replaced
115:289c7667adab | 116:fc2ff128835a |
---|---|
15 | 15 |
16 - implement ack, then fallback to recording if not ack'd | 16 - implement ack, then fallback to recording if not ack'd |
17 | 17 |
18 - Being able to drag rows up and down the main loot grid would be awesome. Coding | 18 - Being able to drag rows up and down the main loot grid would be awesome. Coding |
19 that would be likely to drive me batshiat insane. | 19 that would be likely to drive me batshiat insane. |
20 | |
21 - Something to NOT do: sort cross-realm recipients into history realms based | |
22 on the realm of the recipient instead of the realm of the player. While this | |
23 would be useful for building up a history across realms... why would you want | |
24 to do that? Massive data piling up that wouldn't be noticed unless the user | |
25 makes a habit of clicking the realm dropdown menu and looking around history. | |
20 ]] | 26 ]] |
21 | 27 |
22 local helptree = { | 28 local helptree = { |
23 { | 29 { |
24 value = "about", | 30 value = "about", |