Re: [Pythoncard-users] workaround for raising child windows in resourceEditor

[Kevin A. <al...@se...>]

On Apr 5, 2005, at 11:12 AM, bra...@om... wrote:

>
> Kevin Altis wrote on 04/01/2005 11:11:20 AM:
>
>
>  > On a related note, I never added lowercase aliases for
>  > Raise and Lower to the Background class because I
>  > wasn't sure if this would be legal since raise is a
>  > keyword and we need it for raising exceptions. If
>  > someone knows the correct syntax so that we can have a
>  > lowercase alias to Raise I'll add it to the class;
>  > perhaps I could just do a setattr or something?!
>  >
>  > raise = wx.Frame.Raise
>
> Are lowercase aliases used for a lot of other names in PythonCard or 
> wx?

wxPython wraps wxWidgets, which is C++ and the naming convention there 
is CamelCase style. All methods and attributes in PythonCard are 
mixedCase style, even if they are simply aliases for wxPython methods. 
This makes it easy to see where you are using wxPython methods and 
where you're using PythonCard framework code.

In the PythonCard shell, I added code that excludes CamelCase wxPython 
methods from showing up in the auto-complete list so that you wouldn't 
see 150+ extra confusing method names all the time, but if you type 
something like self.Show( you'll notice that the wxPython methods are 
still there and available if you want to use them.

ka