So now I’m wondering if there’s a binary I can get my hands on that got compiled between August and now (I don’t want to have to whip out MSVS, etc :))
···
On Monday, March 4, 2013 5:19:00 PM UTC-5, Adam Duston wrote:
I’m using wxPython 2.9.4 on Windows. When I try to instantiate a wx.FileSystemWatcher, I get an AttributeError. Looking through the attributes of wx, I see a number of types that start with “File”, but no FileSystemWatcher. Any quick suggestions?
So now I'm wondering if there's a binary I can get my hands on that got
compiled between August and now (I don't want to have to whip out MSVS,
etc :))
There is, but it wouldn't help as FileSystemWatcher still isn't in Classic, and probably won't be since almost all of my attention is on Project Phoenix these days. It is in Phoenix already though.
There is, but it wouldn’t help as FileSystemWatcher still isn’t in
Classic, and probably won’t be since almost all of my attention is on
Project Phoenix these days. It is in Phoenix already though.
Thanks very much for your reply! I was actually able to start using the code from a snapshot build of Phoenix (Index of /Phoenix/snapshot-builds). I noticed with some consternation that a number of functions and classes appear to be missing from Phoenix: http://wxpython.org/Phoenix/docs/html/classic_vs_phoenix.html . Would you recommend that new projects use Phoenix from now on, or is it safer to stick with Classic for now?
Thanks again!!!
Adam
···
On Monday, March 4, 2013 9:23:01 PM UTC-5, Robin Dunn wrote:
Adam Duston wrote:
Aha, putting this together a bit more now. Looks like FileSystemWatcher
So now I’m wondering if there’s a binary I can get my hands on that got
compiled between August and now (I don’t want to have to whip out MSVS,
etc :))
There is, but it wouldn’t help as FileSystemWatcher still isn’t in
Classic, and probably won’t be since almost all of my attention is on
Project Phoenix these days. It is in Phoenix already though.
There is, but it wouldn't help as FileSystemWatcher still isn't in
Classic, and probably won't be since almost all of my attention is on
Project Phoenix these days. It is in Phoenix already though.
Thanks very much for your reply! I was actually able to start using the code
from a snapshot build of Phoenix
(Index of /Phoenix/snapshot-builds). I noticed with some
consternation that a number of functions and classes appear to be missing
from Phoenix: http://wxpython.org/Phoenix/docs/html/classic_vs_phoenix.html
. Would you recommend that new projects use Phoenix from now on, or is it
safer to stick with Classic for now?
I believe that list needs to be revisited a bit (but not that much, I
guess). In any case, what's missing is mostly very minor/corner cases
classes, and I bet you can build a perfectly working Phoenix
application without even looking twice at that page.
If you're starting now with wxPython, I would suggest you give Phoenix
a serious try, as it is the future. It may be slightly harder for us
oldies to adapt to the new framework, but not that much in the end
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
Unfortunately, I can’t get even a very simple version of my UI to work in Phoenix. I attached a file that reproduces the problem to this message. Just put phoenixfailurereport.py and linkedin.png into a directory, then run phoenixfailurereport with wxPython-Phoenix-r73571-win32-py2.7 on windows 7. This will place a linkedin icon in your windows system tray, but right-clicking it will not produce a menu :(. Equivalent code works in 2.9.4.
Instead of complaining about this, I’d love to submit a pull request on github. Is there a quick guide somewhere that will help me wrap my head around the python → wxWidgets interop? When I search the source code for “TaskBarIcon” I get nothing.
Unfortunately, I can't get even a very simple version of my UI to work in Phoenix. I attached a file that reproduces the problem to this message. Just put phoenixfailurereport.py and linkedin.png into a directory, then run phoenixfailurereport with wxPython-Phoenix-r73571-win32-py2.7 on windows 7. This will place a linkedin icon in your windows system tray, but right-clicking it will not produce a menu :(. Equivalent code works in 2.9.4.
Attached still does not show the menu on right click but one can see that "CreatePopupMenu" is called - will see what Robin has to say.
BTW, made some other changes so that the frame shows and that on close everything is destroyed.
Forgot to mention that this is with 73604-win32 on Py 2.7 and Win 7.
Werner
···
On 06/03/2013 16:44, Werner wrote:
Hi Adam,
On 06/03/2013 16:15, Adam Duston wrote:
Unfortunately, I can't get even a very simple version of my UI to work in Phoenix. I attached a file that reproduces the problem to this message. Just put phoenixfailurereport.py and linkedin.png into a directory, then run phoenixfailurereport with wxPython-Phoenix-r73571-win32-py2.7 on windows 7. This will place a linkedin icon in your windows system tray, but right-clicking it will not produce a menu :(. Equivalent code works in 2.9.4.
Attached still does not show the menu on right click but one can see that "CreatePopupMenu" is called - will see what Robin has to say.
BTW, made some other changes so that the frame shows and that on close everything is destroyed.
Unfortunately, I can't get even a very simple version of my UI to work
in Phoenix. I attached a file that reproduces the problem to this
message. Just put phoenixfailurereport.py and linkedin.png into a
directory, then run phoenixfailurereport with
wxPython-Phoenix-r73571-win32-py2.7 on windows 7. This will place a
linkedin icon in your windows system tray, but right-clicking it will
not produce a menu :(. Equivalent code works in 2.9.4.
Fixed. I needed to add some code that tells the runtime that ownership of the menu is transferred to C++. (There is a simpler way to do that but apparently it isn't working with an overridden virtual method...) Anyway, the problem was that the menu was being destroyed as it was returned from the function because the Python proxy still had ownership of it.
Instead of complaining about this, I'd love to submit a pull request on
github. Is there a quick guide somewhere that will help me wrap my head
around the python -> wxWidgets interop?
There is some overview info in the Phoenix area of the wiki, and some info in the README in the source tree, but I expect that I've made some assumptions that the reader already knows a lot and can read my mind too so it probably won't be very newbie friendly.
As for PRs, keep in mind that the master source repo for wxWidgets, wxPython and Phoenix is still a subverison repository. So the repos in the wxWidgets project on github will not accept PRs and the wx devs will rather get patches via Trac. I've got my own clones on github which I'm working from now, so we can try doing PRs there if you want and see how it works out.
When I search the source code
for "TaskBarIcon" I get nothing.
