if your reporting memory concerns then please state if your running embedded or disembedded (with externals or with out). Because Running with Externals (embedded) is rather a meaningless number unless it's the ONLY rock based addon you have.
im gonna try to be the nicest i can to this guy... but i don't think it worked
Quote from forfeit »
The loosing my placement/settings EVERY TIME I logged in was a pain in the.. well you know.. at first, but now it's just making FuBar pretty much completely unusable. I understand it's a bug, and will be eventually fixed, but in the meantime, alot of us die hard fans, are left with something we completely cant use.
IMHO, and I know people are gonna say my opinion doesn't count, (but seriously isnt that why these mods are made? for people to use?) is that fubar3 isn't, and wasn't, ready to replace the FuBar we know and love yet.
...but next time, please keep FuBar in the beta/testing phase till at least the MAJOR bugs are removed. I think a lot of people would have had a better outlook on FuBar (and Rock) if their plugins/settings didn't all get messed up and unusable when we upgraded to something that was announced to be ready.
yes know glitch.. try nuking your SV files for fubar both account and toon lvl, there is prolly a DB migration issue.
"These are BETA addons you are updating and you should expect to see cutting edge features which may not be fully functional or bug-free. If this doesn't sound appealing for you, stop reading this page and update your addons through release versions from mod sites instead. Some addons are more beta than others."
hehe .. one should expect it to fubar every once in a while... as a beta tester for fubar3 while it was in the branches it was rather stable and didn't really bug on me any more than the trunk one was.
But as development to production is, it was moved from branches (a place for an author to test things on his own) into trunk (to see how things fair where others are going to use and develop off it) things broke in a rather unpredictable way. Your comment of "please keep FuBar in the beta/testing phase till at least the MAJOR bugs are removed" is rather ...
if that's the case then contact the authors of those plugins (via forum thread) about it ... it stands to reason that the perticular plugin locations are saved both in fubar and in the plugin it self SV file...
This is with the latest FuBar (r49191.12) and FuBar_LocationFu (r47093.9).
[2007/09/19 16:30:51-67-x1]: AceEvent-2.0-49287:1069: Usage: AceEvent20Frame:RegisterEvent("event")
AceEvent-2.0-49287:1078: in main chunk
<in C code>: ?
<in C code>: in function `pcall'
FuBar-49053\FuBar.lua:811: in function <Interface\AddOns\FuBar\FuBar.lua:806>
FuBar-49053\FuBar.lua:924: in function `LoadPlugin'
FuBar-49053\FuBar.lua:1052: in function <Interface\AddOns\FuBar\FuBar.lua:1044>
<in C code>: ?
LibRockTimer-1.0--51719 (FuBar):289: in function <...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:227>