Here's my responses to your recommendations:
1. Unfortunately, I could not get this solution to help me with my issue... Although I acknowledge that your code will position the ToolTabStrip autohide component on the Right [if it exists], it doesn't work when the toolWindows are hidden. At the time they're hidden, the ToolTabStrip reference is null, and so you are unable to set that property, as you mentioned. When they are unhidden, via the autohide() method, the property is set to auto, and the window docks to the left, also as you mentioned. It seems to be a bug that they do not assume their proper position as delineated at design time, but they do if you call show() prior to calling autohide(). So, in summary, when you call show() on a toolwindow in a hidden state, it goes to the correct position, but when you call .autohide() on a hidden toolwindow, it does not. In an attempt to workaround this issue, I tested about 25 events to see if I could insert your code in between the .autohide() call and the docking of the window on the left. Although some of my events were fired, and I set that property as you suggested, it failed to position the toolWindow on the right. I've also tried explicitly setting the ToolTabString.AutoHidePosition property without testing for the relationship in advance. I can't get anything to work, so I'm still stuck with my other bad workaround. If you test this scenario, I think you'll find that it is very difficult, if not impossible to go from hidden to autohidden on the predefined side of the screen. Any solution you can come up with would be greatly appreciated.
2. Using your recommendation, I've gotten around this issue [i think] by handling the ActiveWindowChanging event of the RadDock during form initialization and cancelling all of the events. However, it was sporadic before and maybe I'm just getting lucky. I'll repost after you get back to me about the other two.
3. On this one, I've now seen the behaviour act both ways, so I don't see how it can be as designed, haha. I mean that while originally I saw it behave as described below, it now behaves the way I want, and I haven't changed anything! In addition, the open animation and clicking on the tabs has proven to be extremely buggy. Sometimes hovering over the tab will not cause it to slide out, but clicking it will. Sometimes, it takes several clicks to open, and sometimes it does not open at all. Sometimes everything seems to work just fine. Another weird case of randomness in computers, which are not really supposed to act randomly ;-) The last thing I will note is that I've noticed that the AutoHideAnimation is defaulted to only when it slides out. I figured it would be nice to slide both ways and tested that setting. Now I see why the default is the way that it is. The painting on the slide in animation is bad, causing the area that the tab once took up to not be painted. Instead, you just see the repeated left (or right) edge of your toolwindow until the animation finishes, at which point it all clears.