Please sign in to comment.
Don't move wxTextCtrl insertion point if it doesn't really change
Resetting the insertion point position to 0 after calling wxTextCtrl::SetValue() or ChangeValue() which didn't really change the control contents was unexpected, as such calls are supposed to be "optimized away", and this was indeed the case under wxMSW and wxOSX, but not in wxGTK. So change wxGTK to follow the other ports, add a unit test checking for this behaviour and officially document it. As a side effect, this ensures that the numeric validator classes don't reset the insertion point position to 0 on every focus loss under wxGTK, as happened before.
- Loading branch information...
Showing with 14 additions and 3 deletions.