If you look closely, you'll see that it's not merely an indentation change. The bulk of the function used to be inside a large condition, but that has been changed to an early return. Still, it would have been a little nicer if it had been done in two commits.
Basically it just adds a one line check near the top of a ShowTooltip() function for whether "doc->HasFocus(IgnoreErrors())", and, if not, returns early.
i always struggle with this. i usually end up with code changes first because i want to test code before committing, which means i can't commit a whitespace change before i know the code change works.
and every time i think about the problem i stumble over python where the two can't be separated.
i believe in the end a better solution would be to mark whitespace changes in a different color. or even better mark each character that changed, not just the line.
If so - is it normal to do indention changes and actual code changes in the same commit?
Personally, I would first have committed the indention changes and then did a second commit with the coded changes.