I noticed that Phoenix no longer uses the proxy C++ class wx.PyValidator but uses just wx.Validator. That's a good thing.
Anyhow, I want to learn a little bit more about wx.Validator.TransferToWindow and wx.Validator.TransferFromWindow methods. They are not well documented and examples of them on the Internet just override the methods with a "return True" line and that's it.
When would one override those two methods with some actual code other than just put "return True" in the methods' body?
Or is it that all you really need in any case, is just to override the wx.Validator.Validate method and make it return False for some invalid input but return True for every other input?
I use it to "data enable" controls, i.e. load data from/to the database from/to the controls.
Sample of this can be seen in the medialocker sample application I and Mike have done some time ago. If you find issues with it related to Phoenix can you create an issue or let us know directly.
I noticed that Phoenix no longer uses the proxy C++ class wx.PyValidator but uses just wx.Validator. That's a good thing.
Anyhow, I want to learn a little bit more about wx.Validator.TransferToWindow and wx.Validator.TransferFromWindow methods. They are not well documented and examples of them on the Internet just override the methods with a "return True" line and that's it.
When would one override those two methods with some actual code other than just put "return True" in the methods' body?
Or is it that all you really need in any case, is just to override the wx.Validator.Validate method and make it return False for some invalid input but return True for every other input?