shenjoku
25-12-2011 01:12:00
There's a bug in Widget::_destroyChildWidget(). Instead of just doing:
It's doing something weird, which is changing the order of the data in some cases:
This is causing some issues since the order matters in a lot of cases.
mWidgetChild.erase(iter);
It's doing something weird, which is changing the order of the data in some cases:
*iter = mWidgetChild.back();
mWidgetChild.pop_back();
This is causing some issues since the order matters in a lot of cases.