Yeah, that makes perfect sense. Presumably you have a property of type ObservableCollection<Room> that you are binding the ItemsSource of your FabTabControl to I would bet. Basically you've got 3 ways to workaround this (I think):
1. Set ShowContentTab="False" on your FabTabControl. This will turn off the ContentTab functionality and therefore you will only have Rooms in your ItemsSource (behind the scenes FabTab tries to add a ContentTabView to your ItemsSource whenever
there is more than 1 tab in the control)
2. Expose the property on your viewmodel as ObservableCollection<object> or ObservableCollection<DependencyProperty>---any type that your Rooms and FabTab's ContentTab view actually both subclass. This is a little ugly, but requires no FabTab
source to be changed.
3. Since FabTab is open source, feel free to use a "one off" version of it--perhaps add an interface to FabTab's source, call it IView or something, them make your Rooms also implement that interface--then on your ViewModel expose an ObservableCollection<IView>
or something like that.
Don't forget, be sure to grab the latest changeset of FabTab, not the latest release if you want it to work (somewhat) well with the MVVM pattern.
Let me know what you end up doing.