Change in behavior - TabbedComponent


Since the last change in this class, the 1st call to addTab() does not trigger a call to currentTabChanged() (unlike the way it used to be).


Doh! Thanks, I’ll sort that out!


Um… I just had a look at the behaviour in the demo app, and it certainly does call currentTabChanged() when the first one is added… (?)


Oh, It’s my fault!!, sorry for wasting your time!