Authors CurseForge

Quote from Seerah »

Most of my plugins I have hidden.

Most addons are disabled though if you hide their fubar icon, right?

Quote from Seerah »

As to your 27 plugins - are they all things that you need to see *all* the time? Most of my plugins I have hidden.

Here's the list of FuBar plugins whos positions are resetting each time I log or reload UI:

- Assessment
- DeuceCommander
- ExperienceFu
- FactionsFu
- FriendsFu
- GuildFu
- LoggerHead
- MailFu
- MoneyFu
- Name ToggleFu
- Niagara
- Omen
- PerformanceFu
- Violation
- WhisperFu

Though a few of these wouldn't be needed to be displyed most of the time (Assessment, Omen, Violation), I have them displayed to easily show/hide their frames. All the rest present data that is helpful to have as part of my normal UI.

And to note, I just tested r49339 and the issue still exists.

Fubar 3.0 is not losing my plugin placement but ever since updating I?m getting a problem with Fubar_Factions.

Date: 2007-09-20 15:34:31
ID: 51
Error occured in: Global
Count: 1
Message: ...s\FuBar_FactionsFu\Locales\FuBar_FactionsFu.enUS.lua line 1:
Cannot find a library instance of AceLocale-2.2.
Debug:
[C]: ?
[C]: error()
...dOns\FuBar_FactionsFu\Libs\AceLibrary\AceLibrary.lua:512: AceLibrary()
...s\FuBar_FactionsFu\Locales\FuBar_FactionsFu.enUS.lua:1: in main chunk
AddOns:
FluidFrames, v1.4
FuBarFactionsFu, v2.2
FuBar, v49053
KLHThreatMeter, v20.4
Stubby, v1923
Swatter, v4.0.4

I?ve tried deleting both Fubar & FuBar_FactionsFu folders and re-installed but I still get the error everytime I log on.

Also: I have no idea if this is related to FuBar 3.0, Rock, or something completely different, but I've been getting the following two errors whenever my UI reloads or I login ever since the big Rock changeover earlier this week:

[2007/09/20 18:51:55-1141-x1]: IFrameManager\IFrameManager.lua:2: attempt to call global 'IFrameFactory' (a nil value)

[2007/09/20 18:51:55-1141-x1]: IFrameManager\IFrameManagerCapsule.lua:2: attempt to call global 'IFrameFactory' (a nil value)

OK the problem with the buffs seems to be fixed but another one appeared: Some FuBar-Plugin-Symbol's positions aren't saved. So they return to "standard positions" when you leave the game and relog.

Until this bug is fixed too, I'll continue to use the last Ace 2 Build of FuBar.


Greetings

Timo

For some positive rantings...I like the new fadeout of the rock menu when my mouse is off the config panel.The new mod menu options is nice, just wish the list would stay open after I select a mod in case I wanna select another. I'm really liking the performance gain on my game..fps was up to 65 last nite, haven't seen that in a very long time and I'm STILL running crap loads of mods.For me, if I log into a character I select a profile, then I usually copy one from another toon...then I log out. Come back in and set up my toon.That doesn't fix all the issues with things moving around but it helps a lot.

CowTip does NOT work with Fubar 3.0
and im reverting. I prefer to have Fubar config somewhat separate to my other mods.

Meaning i want a menu to config fubar and i want a menu where i can config the mods located on fubar. Not 1 menu for everything.

Niagara/waterfall was essentially the best combo i know.
As for old dropdown menus being 'clunky', well although im not against change, its a bit about doing it gradually. This way rock can actually be released and actually be at an even more improved state than how it was released now.

Right now i was a bit caught of guard with rock config and honestly didnt like it, but make it a more progressional release (smaller steps) towards what you have in mind with rock and what the old fubar was and it could be a great hit.

I updated FUB-25 on Jira with some more details as well as a SV file before load and after exit, as well as a list of other ace addons I use in case this is a library issue.

Something's definately screwy, as after exit some plugins appear on both the top and bottom panels in the SV. Assuming the process of writing the in-memory state to the SV is not broken, that suggests that the problem is in the placement when you have two panels. It places all the plugins that the SV tells it to place on the top panel, then looks for unreferenced plugins (the way it would for a newly installed addon) and also places them on the top panel instead of checking if the unreferenced plugins are actually referenced on the bottom panel.

I haven't seen much in the way of specifics from people in this thread as to where things are ending up vs where they should be, but for me it has always been a plugin that should go on the bottom panel getting placed on the top. I haven't seen a situation where a plugin that my SV says goes on the top gets placed on the bottom. If other's experience is the same, that would match my theory, but I haven't looked at the FuBar code yet -- I'm just speculating based on what I see in-game and in the SV file.

While I appreciate the new Fubar 3.0 - I'm not seeing the benefit. When I rt click on the fubar it now gives me the rock config which is really cumbersome. I'd like to have that popup menu back to enable/disable fubar modules. If I want the "niagra" look I'll use Niagra.

I'm reading about how it messes up settings - which 2.0 did frequently for me. It would rollover changes from one toon to another even though they are on separate profiles. If 3.0 is still doing this, or worse, why switch?

Has anyone had any issues going back to Fubar 2.0 after going to 3.0? Anything special need to be done?

Quote from Fonex »

I haven't seen much in the way of specifics from people in this thread as to where things are ending up vs where they should be, but for me it has always been a plugin that should go on the bottom panel getting placed on the top. I haven't seen a situation where a plugin that my SV says goes on the top gets placed on the bottom. If other's experience is the same, that would match my theory, but I haven't looked at the FuBar code yet -- I'm just speculating based on what I see in-game and in the SV file.

Like you, what I've primarily been seeing is mods that 'should' be on the bottom panel getting junked into the top panel. Often piled on top of each other to the extent that I can only actually use one or two of my (many!) FuBar mods. Given that some of these mods are fairly important to me (Closetgnome etc) I fear I'll also have to revert tonite.

Yes, yes, if you would read the thread (and it's only up to 4 pages, so it's not like that should be much to ask), you'd see that many people are having an issue with positions not being saved and that it will probably be fixed in the future. Until then, you are more than welcome to use whichever version of FuBar you want to!

I've been looking at the bug where plug ins move from bar 2 to bar 1 and I've tracked it down a problem where a nil panelId is being passed to FuBar:ShowPlugin. This causes FuBar to put the plug in on panel 1 instead of the configured panel.

I'm not sure if this is the RIGHT solution but I've fixed it by making the following changes to the FuBar.lua file:

Change line 1299 from:

		panelId = 1

to

		panelId = self:GetConfiguredPanel(plugin);

Add the following to the end of the file:

function FuBar:GetConfiguredPanel(plugin)
	panelId = 1;
	for _,panel in ipairs(self.db.profile.panels) do
		if panel and panel.plugins then
			for _,part in pairs(panel.plugins) do
				if part then
					for i,loop_plugin in ipairs(part) do
						if (loop_plugin == plugin:GetTitle()) then
							return panelId;
						end
					end
				end
			end
		end
		panelId = panelId + 1;
	end
	
	return 1;
end

It seems like the proper panelId should be getting loaded from somewhere else but I didn't have the time to get much deeper to see what is going on. This fix is probably just a band-aid for now.

Quote from Fonex »

I updated FUB-25 on Jira with some more details as well as a SV file before load and after exit, as well as a list of other ace addons I use in case this is a library issue.

Something's definately screwy, as after exit some plugins appear on both the top and bottom panels in the SV. Assuming the process of writing the in-memory state to the SV is not broken, that suggests that the problem is in the placement when you have two panels. It places all the plugins that the SV tells it to place on the top panel, then looks for unreferenced plugins (the way it would for a newly installed addon) and also places them on the top panel instead of checking if the unreferenced plugins are actually referenced on the bottom panel.

I haven't seen much in the way of specifics from people in this thread as to where things are ending up vs where they should be, but for me it has always been a plugin that should go on the bottom panel getting placed on the top. I haven't seen a situation where a plugin that my SV says goes on the top gets placed on the bottom. If other's experience is the same, that would match my theory, but I haven't looked at the FuBar code yet -- I'm just speculating based on what I see in-game and in the SV file.

I had tested this, but it's not the placement of the Panels, but rather Bar 2 to bar 1.. I had tested this by deleting my top Panel, and relogging, this made all mods bump to the bottom bar (which was now Bar 1) and when I recreated the top bar (now bar 2) and logged, all mods I had placed on the new top went back to the bottom (bar 1).

Works for me. Thanks for this bandaid! Only had FactionsFu forget where it went.

Yay!

Just updated to the latest FuBar, and the ones that used to move around were just missing instead... I re-added them in the Rock GUI, logged out, back in, and they stayed where they belonged!!!

Thanks for getting this working again!!!

Quote from Seerah »

How so? I'm using both perfectly fine. CK (I'm assuming) even tested them against eachother, since they're both his mods and both use the Rock framework now.

Well i couldn't get mine to work. It seems the version i downloaded using WAU didn't have that rock config setting thingy built in it so it wouldn't even load the mod.
/cowtip didn't work either.