Einfach in den Optionen die Anzeige von Spielern, die nicht in der Gruppe sind, aktivieren. Da nur Daten fuer Spieler in der Gruppe aufgezeichnet werden, werden dadurch auch keine falschen Spieler angezeigt.
PS: Eigentlich sollten wir hier doch englisch schreiben, oder? ;-)
ist doch standardm??ig aktiviert (Auge - nicht in Gruppe), Screen ist ja weiter oben, die Daten werden gesammelt und auch angezeigt, wenn er/sie die Gruppe verl?sst aber nicht mehr.
w?rde ich ja gern, hatte englisch in der Schule sogar eine 2, nur bin ich 1990 raus und brauchte es seitdem nicht mehr aktiv, d.h. ich kann nichts mehr. Noch schlimmer ist es als Ossi aber mit der 1. Fremdsprache, Russisch 1, schreiben kann ich gar nichts mehr und w?rde auch nur noch einen Satz verstehen.
I think I have an idea why people disappear after leaving group and it's related to data collection/cleanup. Is there a chance that the folks who say another combatant disappear saw them engage in any combat log relevant activity just after they left the raid group? If that's the case that would explain it.
Unfortunately fixing this cleanly will take some reworking of how combatants are created and retained and it will likely affect what specific combatant filter options Recount can use can honor (i.e. I may have to kill the non-trivial vs trivial mob distinction). So give me a little time to do this properly.
This doesn't really explain why one would lose combatants mid-raid though if people have experienced that. So let me know if that was the case.
Can you give details, there are many possible causes, most likely is Recount's sync code. Also Recount certainly handle's healing data differently than WWS, though the differences shouldn't be completely massive (or rather they should be as massive as lifebloom, PoM and ES contributions can be, plus some error in overhealing estimation on WWS side).
@cremor: I don't really understand why this is an important issue. Xin and Nev in that thread kind of give two perspectives on the story. Having it as optdep does no harm as I see it beyond one possibly getting an extra disembedded libstub and callbackhandler directory, which is tiny and far less hard drive damage then having both hard-embedded with every lib that needs them, which is the current dogma. I'll remove the optdeps when I get around to it, but in reality this just isn't a cleanly resolved issue and it's not even an important one, having the optdeps and x-embeds this way will never ever break anything for an addon. A lib on the other hand doesn't have that freedom but recount isn't a lib.
Of course this isn't an important issue, but I'm a little bit perfectionistic, so please excuse me ;-)
Fact is, that many people say that the standalone LibStub shouldn't be in trunk. And a standalone version of CallbackHandler-1.0 isn't in trunk and has never been there. So there really isn't any reason to have it in the OptionalDeps or X-Embeds.
If I use an addon with externals, LibStub and CallbackHandler-1.0 are included by svn:externals and embeds.xml, OptionalDeps and X-Embeds are not needed.
If I use an addon without externals, LibStub and CallbackHandler-1.0 are loaded by the library which needs it because if a library gets loaded standalone not only its lib.xml is loaded but also the lib.toc, where LibStub and CallbackHandler-1.0 are referenced. So OptionalDeps and X-Embeds again are not needed.
Quote from Elsia »
Removed libstub and cbh from x-embeds in the toc file, shouldn't have any adverse side effects but let me know if otherwise :P
Ok i know it's purely cosmetic and not important but this is driving me mad. I'm trying to put recount in the bottom left of my screen, aligned with chatframes and bars but whenever i relog or reload UI, the window has moved from like 2 pixels on the left, 2 pixels to the bottom and size has changed something like a 1-2 pixels too, no matter if i lock the window or not, i even tried to change the x/y settings and size by editing the lua, didn't work.
Is there something I am totally missing in the settings or is there no way to prevent recount from keeping segments where people are killing critters? I like to look at trash pulls sometimes to see if people are slacking, what happened to people, etc, but retards killing critters between pulls are filling my segement log with "snake" etc.
I don't know why this is happening but it seems to me that for some reason Recount is going a little spaz after every time I log in.
Here's what I do.
Recount is set to auto hide on combat, as it sits above my omen window, showing only the damage or threat depending on out/in combat.
I clear all data in recount
Starts working perfectly as expecting hiding/showing changing the numbers etc.
Window is now showing there with the old previous value I logged out with (Correct)
Window now does NOT hide on combat.
Window now does NOT update the number, leaving it locked at the previous value I logged in with.
To fix the issue, I have to clear all current data again, and it starts to work fine.
Is this an issue others are seeing or just me ? Happening on my hunter and a few alts aswell.
@hal: Don't see the problem on my 1200x1024 display, may have to do with rounding of numbers for the larger display. I'm not quite sure how to address this. Does it drift (i.e. change a pixel or two per relog), or just offset once?
@all: Fixed a bug that kept miss types (block, dodge, parry etc) from being recorded under certain filter conditions (including the default one :P)
I use the Emblem font and the change was quite noticable. The window looked very "crowded". I reduced the bar height and that reduced the font size to something that looked a bit more reasonable so I'm happy now.
To explain the change. Before it used 75% of the bar height for font. Now it uses a 2 pixel gap or 75%, whichever makes the font bigger, this means that for large bars it will use larger fonts, but it shouldn't crowd small fonts. I can also go for a compromise, of say a 4 pixel gap or 75% if that looks better for folks.