StatBlock_Memory
A Data Broker plugin for displaying memory usage, also has a tooltip for per addon usage.
Works with any Data Broker display addon.
You can limit the number of addons displayed (e.g. 20) in the tooltip with the following command:
/script SB_MEM_KILL = 20
Comments
-
Funkeh Owner
-
View User Profile
-
Send Message
Posted Aug 5, 2016how do i get this to work with bazooka?
-
View User Profile
-
Send Message
Posted Aug 5, 2016-
View User Profile
-
Send Message
Posted Oct 21, 2016Works without problems on bazooka!
-
View User Profile
-
Send Message
Posted Dec 15, 2014doe this require the StatBlock Core addon to work? It's not stated anywhere that it does.
When I installed this without the Core I couldn't find it anywhere even though it was turned on. It didn't show up in the Bazooka plugins list at all.
Once I installed Core it showed up, but since I already run Bazooka I don't need another LDB display addon.
-
View User Profile
-
Send Message
Posted Dec 15, 2014No.
-
View User Profile
-
Send Message
Posted Dec 19, 2014Then I'm not sure why but it doesn't work with Bazooka bars.
-
View User Profile
-
Send Message
Posted Oct 19, 2013Getting this message every 30 seconds or so while running statBlock. I don't have to do anything in particular. Reloading UI causes it to go away sometimes but not others.
Message: StatBlock_Memory\StatBlock_Memory-v5.4.0.lua:65: attempt to index upvalue "obj" (a nil value) Time: 10/19/13 20:16:37 Count: 11 Stack: Locals:
Running version for 5.4
-
View User Profile
-
Send Message
Posted Oct 19, 2013Is it possible you're running another addon that is also trying to create an object called "Memory"?
-
View User Profile
-
Send Message
Posted Nov 14, 2012Ok, v5.0.5.2 will automatically stop updating in combat for users with so many addons that it would cause an error, due to how long it takes to process them all. See the new screenshot for the new tooltip clarifying this.
-
View User Profile
-
Send Message
Posted Oct 22, 2012232x StatBlock_Memory\StatBlock_Memory-v5.0.5.lua:43: script ran too long
StatBlock_Memory\StatBlock_Memory-v5.0.5.lua:43: in function <StatBlock_Memory\StatBlock_Memory.lua:42>
Locals:
-
View User Profile
-
Send Message
Posted Oct 22, 2012Are you running on a really poor PC or something? It's complaining that the Blizzard function for updating the addon memory display is taking too long, not this addon, which needs to be done for this addon to function.
-
View User Profile
-
Send Message
Posted Nov 10, 2012I am seeing this error on occasion, seems to always happen just on the first fight of a raid or dungeon, not consistantly but often enough to be noticable. Is it a "can't do that in combat" kind of error? Its pretty much random, but seems to always happen in combat.
-
View User Profile
-
Send Message
Posted Nov 10, 2012@Anteract
Yes, the "script too long" errors will only happen when you're in combat, Blizz doesn't restrict time out of combat. There's nothing I can do other than stop this addon updating during combat, but some people may want memory updates during combat that don't suffer this dumb Blizzard restriction.
I think it's best to just ignore it because there's no way for me to check if specific PC's will be able to run this function fast enough or not to even trigger this error. If it still persists after patch 5.1 I may just kill it in combat. But since it's a Blizzard function throwing up the error, it may (hopefully) be optimized in the next patch.
edit: Actually, could you tell me how many addons you have enabled? It could be that Blizzard's function is only throwing the error for people with a lot of addons, as that would take longer to process.
-
View User Profile
-
Send Message
Posted Sep 23, 2012The text display setting always resets to MB a few seconds after logging in, despite whatever you may have it set to.
-
View User Profile
-
Send Message
Posted Sep 24, 2012That will depend on the display addon you're using, which one are you using?
-
View User Profile
-
Send Message
Posted Feb 8, 2009Funky note that you should add the type = "data source" field to your ldb object else it will fail to load on various display plugins, tekkub stated its required on wiki.
-
View User Profile
-
Send Message
Posted Nov 26, 2008I added a little bit of code to be able to sort the list by Name (Ascending and Descending). In StatBlock_Memory.lua:
1. Add the following two functions under mySort:
<<code>>local function mySort(x,y) return x.mem > y.mem endlocal function mySortName(x,y)
Vux return x.addon < y.addon endlocal function mySortNameDescending(x,y)
Vux return x.addon > y.addon end<</code>>-----2. And in function Mem.obj.OnTooltipShow(tooltip):
<<code>>table.sort(memTbl, mySort)Comment this outif( IsShiftKeyDown() ) then
Vux table.sort(memTbl, mySortName) elseif ( IsControlKeyDown() ) then table.sort(memTbl, mySortNameDescending) else table.sort(memTbl, mySort) end<</code>>------ Hold Shift and then mouseover the icon and the tooltip will be name sorted in alphabetical order.
- Hold Control and the tooltip will be sorted in backwards alphabetical order.
- And of course, don't hold either button and it's sorted by total memory usage (as normal) :)
Any chance you might be able to add this to the next version?
Anyway, just thought there might be others out there who might have wanted this feature as well :)
- Vux of US-Dragonblight