If we call QAstractItemView::mouseMoveEvent in the if statement at the beginning the error does not occur and we still fire the entered(...) signals.
I'm not completely sure why this fixes the issue. Another alternative would be to call setState(NoState) at the end of
mouseMoveEvent and by this reimplementing some Qt logic.
If we call QAstractItemVie w::mouseMoveEve nt in the if statement at the beginning the error does not occur and we still fire the entered(...) signals.
I'm not completely sure why this fixes the issue. Another alternative would be to call setState(NoState) at the end of
mouseMoveEvent and by this reimplementing some Qt logic.