Couldn't find any mention of this when I searched the thread, but I've found severals addons don't seem to remember their positions. I wondered why this happens.
For example ammo_fu seems; If it's disabled on one profile (example:Druid) and you log out then in again it'll be on the minimap.
Or, with the example of BigWigs and Bugsack they never remember whether they were put on the minimap and don't seem to have per profile saving. Per porfile I don't mind, but I'd like to keep them on the minimap.
Anyway, does anyone know why these things would occur?
I have the same issues and its not the same plugins each time. At first I thought it was the latest plugins installed, then upon another session random plugins had moved around at will. Latest SVN with a clean install on every plugin....also deleted ALL of my saved variables.
I thought I should mention this here. The FuBar 2.0 available in WoWInterface.com is outdated, so newer Ace2 addons cause it to break (hard! nothing appears!) with this error at logon:
Panel.lua:110: AceOO-2.0: Improper self passed to init. You must do MyClass.super.prototype.init(self, ...)
This also seems to affect the KC_PlayerFramePlus version I have installed.
A question: if a newer Ace2 library version isn't compatible with previous addons, shouldn't this library receive a new number, so that it didn't make them break due to API changes? If that's the case then this "AceOO-2.0" should probably be named "AceOO-2.1" or something like that, and work side-by-side with the older one. Or am I mistake?
As I understand it, Ace 2 will use the latest revision of whatever file you have loaded.
so if Ace2 revision 100 comes from FuBar at WoWI, and you pick up UberAceAddon from the SVN which has Ace2 revision 2000, the FuBar addon will use Ace2 revision 2000.
That's how I understand it too. But things won't work if from version 100 to 2000 the API itself changed, because then the older v100 addon will be calling methods that don't exist in v2000, or will pass to them parameters in a (now) invalid format. This is what seems to be happening.
The way things are now, using the newer FuBar_VolumeFu, or the newer BigWigs, or the newer TinyTip (and I mean newer in WoWInterface, not in the SVN), all cause the official FuBar (the one available at WoWInterface) to break, as well as some older Ace2 addons. Something very, very important changed in the API, and older addons officially released, beginning by FuBar, must be urgently updated at the official repositories.
Either this, or the addons using Ace2 should be flagged as beta until the API becomes stable. Otherwise those who download them thinking they're final versions will come to the conclusion that anything Ace2-based is very unstable.
ckk changed something in AceOO and it caused a bug. Bugs happen, geeze.
The whole point of the embed design is that we try to never break older mods. If the API changes in some breaking way then a whole new major version is declared. Old mods will still use their old version, and the two versions can exist side-by-side.
was trying to reposition everything in my fubar panels and save into char profiles, kept getting the following error whenever I tried to click something off ( happened on about 90% of the addons listed), the check would stay on the addon would not be removed till I either reloaded after saving profile or I clicked on one that didn't give me the error then all the others would clear and be removed. Here is the recorded error by Buggrabber:
["message"] = "[2006/08/14 20:39:10-58]: FuBarPlugin-1.2\\FuBarPlugin-1.2.lua:566: attempt to index field `?' (a nil value)\nFuBarPlugin-1.2\\FuBarPlugin-1.2.lua:566: in function `?'\nDewdrop-2.0\\Dewdrop-2.0.lua:466: in function <...erface\\AddOns\\FuBar\\libs\\Dewdrop-2.0\\Dewdrop-2.0.lua:421>\n\n ---",
["time"] = "2006/08/14 20:39:10"
Not sure if it's in FuBarPlugin-1.2 to actually in Dewdrop-2.0, I had updated to whatevers in SVN trunk earlier that same day.
After the last update to FuBar things got back to normal. More or less, anyway, since this positioning bug, where the position I put some plugins isn't remembered, is also affecting me. Trying to fix this I looked at the contents of FuBar.lua in the SavedVariables folder and noticed that the plugins that "forget" their new position between logons appear there in two or more places (for example, position 3 in right at top bar 2 and position 1 in right at bottom bar 1).
So, my first bet was that there was a bug in FuBar that caused it to not delete from the table the old position while writing the new position for a moved plugins. This, coupled with the order the table is processed when FuBar initializes after a logon, I thought, would cause the plugin to appear in its old position, not the new. So, I proceeded to edit the file and delete the wrong positioning references by hand. I also deleted the FuBar.lua.bak file to be on the safe side. No such luck however. I logged and there they were, wrongly positioned again.
The 3 plugins I use that are presenting this problem are FuBar_MailFu (a version downloaded from the SVN), FuBar_FishingBuddyFu and FuBar_tcgTradeskills (both at the latest version at WoWInteface.com). Oddly enough, one that was presenting this problem, BigWigs, stopped when I upgraded it to the lasted version at WoWInterface.com.
So, either FuBar is itself resetting their positions for no apparent reason, or they have something in their configuration that is causing this, something that BigWigs also had but ceased to have from the a previous version I had to the latest. Actually, maybe both things are true...
I have seen FuBar_MailFu, FuBar_tcgTradeskills, OneView and my own FuBar_PoisonFu (all from SVN) do this. It seems most likely when/if one of the addons has been updated. (Which is strange, but that is the way it feels.)
I'm wondering if these problem addons are all new FuBar 2.0 addons and maybe all the rest are running through the 1.2 compatibility layer?
My Position problems are with FuBar_ExperiencedFu, KeepItCool, FuXPFu, and CombatInfoFu. They remember there psoition but the always start unchecked. Also I'm not sure if Profiles are remembering themselves correctly which might be at the base of this problem. The older addons used to use the old Ace profile methods and Fubar2 uses the new Ace2 profile methods and something may be clashing.
I just swapped to FuBar today so it's entirely possible I'm missing something, but is there a reason "Copy from" under profiles is perma-grayed out? Don't want to clutter WoWInterface or that FlySpray bugtracker if it's not a bug.
I have 2 profiles, one for a main which is the default and one for an alt. The weird thing is the wacky positioning happens on all characters using default (mules) and its different for each one which makes no sense. On one mule character it created like 4 panels at the top of the screen to show the whole 4-5 addons I actually had enabled.
I'm not sure if it is related to the positioning problem but tonight, using the latest SVN version of FuBar and the latest SVN version of the libraries, I could not use the Copy function for the profiles. The menu option is not greyed out but nothing happen when I select a profile to be copied.
Like Azgrim, I only encounter the positioning problem when the default profile is on. I've created a character profile for each one of my alts and the addons are always positioned where I expect them to be.
I also observed that the option frame (with the right click) has some tooltip issues. If there are more then ten lines in the option frame, some lines have empty hint tooltips. These empty tooltips stay at the same position even when we go down or up the options. Here's some pictures so you can see what I mean:
Also, the hint tooltips often end up over the menu tooltips:
This happen for the FuBar menus and for the 2.0 FuBar addons. The 1.2 FuBar addons do not have this issue simply because they do not have hint tooltips.
Is there an easy way to disable those hint tooltips for now?
BTW, I just finished converting all my characters from Titan to FuBar and, quite simply, it rocks. I just don't know why I waited so long cross over :-).
It appears that FuBar does in fact remember the positions... the problem occurs at load where they typically get placed in the default position they would go to as if they have just been installed. If I am now presented with a bar with incorrect positioning I can drag teh addon to the bar where it is supposed to go and it "snaps" into the position where it was saved. This works even when the "default" position is on the left and the "saved' position is on the right. It almost had me convinced that the new fubar had a drag from left side to right side feature.
Currently I have resorted to using only the default profile.. I will have to look into using character specific profiles.