CODEWITHSUNDEEP
pythonwindowslinuxuser-interfacewxpython
Javier
Javier

Reputation: 4623

WxPython differences between Windows and Linux

The tutorials I've found on WxPython all use examples from Linux, but there seem to be differences in some details.

For example, in Windows a Panel behind the widgets is mandatory to show the background properly. Additionally, some examples that look fine in the tutorials don't work in my computer.

So, do you know what important differences are there, or maybe a good tutorial that is focused on Windows?

EDIT: I just remembered this: Does anybody know why when subclassing wx.App an OnInit() method is required, rather than the more logical __init__()?

Upvotes: 1

Views: 2705

Answers (3)

tom10
tom10

Reputation: 69242

I find a number of small differences, but don't remember all of them. Here are two:

1) The layout can be slightly different, for example, causing things to not completely fit in the window in one OS when the do in the other. I haven't investigated the reasons for this, but it happens most often when I use positions rather than sizers to arrange things.

2) I have to explicitly call Refresh more in Windows. For example, if you place one panel over another, you won't see it the top panel in Windows until you call Refresh.

I general, I write apps in Linux and run them in Windows, and things work similarly enough so this is a reasonable approach, but it's rare for me when something runs perfectly straight out of the gate after an OS switch.

Upvotes: 0

Jon Cage
Jon Cage

Reputation: 37516

I've noticed odd peculiarities in a small GUI I wrote a while back, but it's been a long time since I tried to the specifics are a rather distant memory. Do you have some specific examples which fail? Maybe we can improve them and fix the bugs?

Have you tried the official wxPython tutorials? ...or were you after something more specific?

r.e. your edit - You should use OnInit() because you're subclassing wx.App (i.e. it's a requirement for wxWidgets rather than Python) and the wxPython implementation is wherever possible, just a wrapper for wxWidgets.

[Edit] Zetcode has a fairly lengthy tutorial on wxPython. I've not looked through it all myself, but it might be of some help?

The wxWidgets::wxApp::OnInit() documentation is fairly clear:

This must be provided by the application, and will usually create the application's main window, optionally calling wxApp::SetTopWindow. You may use OnExit to clean up anything initialized here, provided that the function returns true.

If wxWidgets didn't provide a common interface then you'd have to do different things in C++ (using a constructor) compared to Python's __init__(self,...). Using a language-independent on-initialisation allows wxWidgets ports to other languages look more alike which should be a good thing right? :-)

Upvotes: 2

Bastien Léonard
Bastien Léonard

Reputation: 61823

EDIT: I just remembered this: Does anybody know why when subclassing wx.App an OnInit() method is required, rather than the more logical __init__()?

I use OnInit() for symmetry: there's also an OnExit() method.

Edit: I may be wrong, but I don't think using OnInit() is required.

Upvotes: 0

Related Questions