-- Tim Roberts, ti...@probo.com Providenza & Boekelheide, Inc.
The reason so much wx code uses Get and Set is because it is interfacing with native code in C and C++, where the concept of a property does not exist.
The reason so much wx code uses Get and Set is because it is interfacing with native code in C and C++, where the concept of a property does not exist.
If this is the case, is there a guarantee that using attributes instead of Get/Set in wx classes is functionally the same?
Werner,
That's what I was looking for. I'll have to rewrite my code at some point then.
Thanks!
--
You received this message because you are subscribed to a topic in the Google Groups "wxPython-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/4v7kJ0PzFks/unsubscribe.
To unsubscribe from this group and all its topics, send an email to wxpython-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Lately I have been refactoring the code of a project, and I wanted to implement extensive use of Python properties. All my code uses Getters and Setters, from the wx classes and my own, so this seems to be no easy task.I checked the wxPython coding guidelines to see if there was any comment regarding the use of Set and Get or properties, but it seems to be a bit outdated by now.
--
--
You received this message because you are subscribed to a topic in the Google Groups "wxPython-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/4v7kJ0PzFks/unsubscribe.
To unsubscribe from this group and all its topics, send an email to wxpython-users+unsubscribe@googlegroups.com.