QTableView doesn't connect to QHeaderView::sortIndicatorChanged until you call QTableView::setSortingEnabled(true). Because signal/slot connections are processed in the order they're made, if you connect to sortIndicatorChanged before enabling sorting, your slot gets invoked before the table is sorted
This is an acceptible and useful behavior except its not fucking documented and I had to read the source code to see why I was always a step behind
I have such a weird relationship with Qt because I work with it professionally and have a Pretty Good Idea of what's going on, but primarily through slamming into it at full force and having to read through its code to figure out why exactly I can't do something. The documentation is just frankly... unacceptable for a product which Costs Money1. Sometimes overridden functions impose restrictions or have specific behaviors and the docs just say "overrides QBaseClass::virtualFunction" or whatever.
afaik the only way to get "good" at this framework without mashing on it is to pay KDAB to come and give you a seminar on some specific part of it.2
-
its a fucking weird situation tho. All of Qt is open source and free for non commercial use and for commercial use you gotta pay. Presumably you get support but I don't think we've ever taken advantage of that. But you get the same shit the hobbyists get, including minimal-effort docs. And a shitload of Qt is contributed by randos, so their docs are just radically inconsistent.
-
and pay them for gammaray which actually shows you sig/slot connections, because there is literally no other way to see that information for an object. I'd have to go rip into private interfaces to get at it, which are obviously not documented and requires I go read source code.