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