Minimap Button Frame 

If you wait a min it will do it on it's own. I have a delay built into it so that it waits to scan until everything is loaded, so it doesn't miss any of the buttons. I can always reduce the delay if it's too excessive.

dlr554

I just had the commented line in there for myself. It really shouldn't be throwing errors. Odd. I'll just pull the line out. - Removed

I've seen the Fubar error before. I thought I had gotten it. It's weird, sometimes the plugin acts like it has a parent and sometimes it acts like it doesn't. Which is impossible of course. - Made a change to how it was referenced. Doesn't throw an error for me, we shall see if it still does when its in a bunch of different configs. Of course that didn't fix it. But I made some more changes and it's fixed now.

I did know about the settings not staying, and I have no clue as to why. I've looked at a bunch of other Fubar addons and they didn't do anything different. I thought fubar took care of all the saved vars for its plugins, but I guess I might have to save the vars for it as well. - My bad. Forgot to add the vars DB to the .toc file. Fixed

I'll try to get them fixed and a new version posted soon.

EDIT: I'm going to make a one quick addition to the addon before I post a new version.
A clean routine to clean up the holes that sometimes appear.

Next version will enable active scanning, we will see if there is any issues with it.

I'll add an option to not show it with the next version.

Until then you can always just remove it from the MBF frame. Then the mail icon will go back to it's normal behavior.

You can also set a key binding to set it to a Key combination instead of command line

Hmmm.... I'm not having any problems with the trinity button anymore. It's been working fine. What version of MBF are you using? Also remember that some addons will gray out their button during combat, and the fact that I try to keep the buttons from moving on the frame could mess things up.

When I was trying to get most of the buttons the same size, I messed around with a little different way of grabbing the buttons. In most cases it worked wonderfully and fixed some small incompatibility issues I've had. But unfortunately it seemed to break the atlas button and the SW_Stats button. I plan on going back and messing with it some more, but thought it would be better to make the addon more feature complete than trying to improve functionality of things that worked pretty well already.

I've seen the weird thing with the moving. It usually happens after I've messed with one of the buttons on the frame that for some reason doesn't want to fully cooperate. The biggest issue is that very few addons handle their buttons in the same way. Some people try to stuff all of the functionality into one function, some seem to think that they need to continually make sure that their minimap button is where they put it. It's almost as if they specifically don't want addons such as mine to move their button.

I haven't run into the lock issue before, but I don't usually keep mine locked. I'll see what I can find on that. I have a couple of ideas on what that might be.

For version 1.7 I have the following features planned and almost finished.

- Multiple Sort selections (Blizz Buttons first, Blizz Buttons Last, Standard Alpha) Done
- Redesigned Options Screen Done
- Ability to show / hide individual Blizz minimap buttons (voice, zoom, worldmap, mail, LFG, Battleground, Tracking, GameTime)
- Fixed an incompatibility with the Bigfoot Addon Done
- Fixed an error with Keybinding Done

Version 1.8 planned

- Manual Button Sorting (drag and drop on the frame)

EDIT:

I looked at the error you received when trying to remove the button. It basically looks to be that whatever you had your mouse over at the time, didn't have a named parent. AKA something funky that should never happen. But I've added another check to the remove to try and catch the only item I know of that doesn't have a parent. (WorldFrame)

EDIT 2:

Finished Redesign of Options Screen

Yeah to remove a button you have to put the cursor over the button you want to remove. Then either use the command line option or the keybinding. This is because MBF attempts to remove the item under the cursor.

Yeah I've seen that. It's because of the way the fishing buddy minimap icon is done and the way that I grab the buttons. I'm hoping to make some changes to the way that the buttons are grabbed in a future version.