I went back to the docs and discovered that it had been there all the time:
If you disable a child of a TabNavigator container by setting its enabled property to false, you also disable the associated tab.
Weird, because I know I searched the TabNavigator help page for the word "disable" like a million times.
The actual property is "enabled" to disable, set it false.
ReplyDeleteThat said, it looks like there is a bug in the TabNavigator that shows the entire navigator as disabled, but _still_ recognizes and dispatches the clicks to the tabs and does the navigation!