Very tough time learning wxPython. Need some kick-starting please!

Hi David,

As with any language/library/etc there is a learning curve :frowning: It is a learning curve that I am still climbing. Unfortunately, one person’s learning curve is another person’s “brick-wall”, so the only thing I can offer is encouragement to keep going and a few other ideas:

  • Consider using wxFormBuilder to help you learn the simple stuff first. Sometimes the visual feedback this tool gives can be very useful and educative.

  • Break down your gui application into bits (i.e. don’t try it all at once). For example, just begin with the would one panel and ensure you’re model is capturing the events generated by it. The wxPython book does describe very well how events are bound to code using the BIND method and the book also does give some insight into implementing the Model-View-Controller pattern.

Sorry I can’t offer more help! Hopefully, others can help more.

Good Luck,

Dermot.

···

On 2 February 2013 04:49, David Lynch d.lynch@yahoo.com wrote:

Hi everyone,

I have been using Python for years and I love it. I’m trying to use wxPython for the past few days and I’m absolutely smashing my head into a brick wall! How in the world do you learn this library? I’ve done every tutorial and looked at many of the included demos. I’ve bought the “wxPython in Action” book and would gladly pay GOOD MONEY to learn what I need to know. I want to master this thing. But I’m at my wits end!

Here is the simple (or so I thought) GUI I am attempting to build. I want three main panels on splitters. I also need a menu bar and status bar. But I have all of that layout working already. Where I am struggling is filling those panels with text/tree widgets and figuring out how the heck to tie everything together with my model.

The first (#1 top left) panel will have a few check boxes and a tree viewer (filled by the model of files on disk.) Clicking on leaves on the tree will activate the second (#2 top right) window to display the appropriate widget for that leaf (or file type from the model.) Some leaves will have configuration pages (checkboxes and dropdowns) and others will have a report list. The bottom panel (#3) will have a scrolling log file, which could simply be the redirection of stdout/stderr, or I could fill it from my logger (in the model) directly. It must scroll like a console window. I feel like I could inherit PyOnDemandOutput() but I can’t figure out how to do it.

What do you think? How can I learn this library to accomplish this task?

Thanks, David.

You received this message because you are subscribed to the Google Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Thanks Dermot. I am not too worried about the layout stuff, although the wxFormBuilder seems to be abandoned, as it is not found on Sourceforge anymore. I was pretty happy with the Bind method description in the book, HOWEVER, I still can’t seem to find the master list of EVT_* events. How do I KNOW that EVT_BUTTON comes from a button click (in the controller class) but EVT_ENTER_WINDOW also comes from the mouse, but doesn’t propagate because it is not a command class event. How would I know if it wasn’t in the wxPython book? I’d like to see the complete list of events so I know what to bind in my handlers. Where are they in the source code even? I searched the source for them and couldn’t find a description of what they are or when they are triggered. Thanks again.

···

On Saturday, February 2, 2013 3:11:25 AM UTC-6, Dermot Doran wrote:

Hi David,

As with any language/library/etc there is a learning curve :frowning: It is a learning curve that I am still climbing. Unfortunately, one person’s learning curve is another person’s “brick-wall”, so the only thing I can offer is encouragement to keep going and a few other ideas:

  • Consider using wxFormBuilder to help you learn the simple stuff first. Sometimes the visual feedback this tool gives can be very useful and educative.
  • Break down your gui application into bits (i.e. don’t try it all at once). For example, just begin with the would one panel and ensure you’re model is capturing the events generated by it. The wxPython book does describe very well how events are bound to code using the BIND method and the book also does give some insight into implementing the Model-View-Controller pattern.

Sorry I can’t offer more help! Hopefully, others can help more.

Good Luck,

Dermot.

On 2 February 2013 04:49, David Lynch d.l...@yahoo.com wrote:

Hi everyone,

I have been using Python for years and I love it. I’m trying to use wxPython for the past few days and I’m absolutely smashing my head into a brick wall! How in the world do you learn this library? I’ve done every tutorial and looked at many of the included demos. I’ve bought the “wxPython in Action” book and would gladly pay GOOD MONEY to learn what I need to know. I want to master this thing. But I’m at my wits end!

Here is the simple (or so I thought) GUI I am attempting to build. I want three main panels on splitters. I also need a menu bar and status bar. But I have all of that layout working already. Where I am struggling is filling those panels with text/tree widgets and figuring out how the heck to tie everything together with my model.

The first (#1 top left) panel will have a few check boxes and a tree viewer (filled by the model of files on disk.) Clicking on leaves on the tree will activate the second (#2 top right) window to display the appropriate widget for that leaf (or file type from the model.) Some leaves will have configuration pages (checkboxes and dropdowns) and others will have a report list. The bottom panel (#3) will have a scrolling log file, which could simply be the redirection of stdout/stderr, or I could fill it from my logger (in the model) directly. It must scroll like a console window. I feel like I could inherit PyOnDemandOutput() but I can’t figure out how to do it.

What do you think? How can I learn this library to accomplish this task?

Thanks, David.

You received this message because you are subscribed to the Google Groups “wxPython-users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-user...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

I tend to us the Phoenix documentation, not complete yet, but I prefer it over the wxWidgets one.

http://wxpython.org/Phoenix/docs/html/Button.html?highlight=button#events-events-emitted-by-this-class
http://wxpython.org/Phoenix/docs/html/TreeCtrl.html?highlight=treectrl#events-events-emitted-by-this-class

http://docs.wxwidgets.org/trunk/classwx_button.html

Werner

···

On 03/02/2013 06:35, David Lynch wrote:

Thanks Dermot. I am not too worried about the layout stuff, although the wxFormBuilder seems to be abandoned, as it is not found on Sourceforge anymore. I was pretty happy with the Bind method description in the book, HOWEVER, I still can't seem to find the master list of EVT_* events. How do I KNOW that EVT_BUTTON comes from a button click (in the controller class) but EVT_ENTER_WINDOW also comes from the mouse, but doesn't propagate because it is not a command class event. How would I know if it wasn't in the wxPython book? I'd like to see the complete list of events so I know what to bind in my handlers. Where are they in the source code even? I searched the source for them and couldn't find a description of what they are or when they are triggered. Thanks again.

It doesn't seem to be abandoned. Here's its page:

Here you can find the nightly builds here (the latest build is dated
November, 2012):

···

On Sun, Feb 3, 2013 at 12:35 PM, David Lynch <d.lynch@yahoo.com> wrote:

I am not too worried about the layout stuff, although the wxFormBuilder
seems to be abandoned, as it is not found on Sourceforge anymore.

--
Alexei Vinidiktov

One quick way to get a list of the events in wx is:

events = [e for e in dir(wx) if “EVT_” in e]

This only gets the main events. There are more in wx.grid for example.

There’s also the “Windows Styles and Events Hunter” app which is pretty helpful too. I wrote about it here: wxPython: Windows Styles and Events Hunter - Mouse Vs Python

  • Mike
···

On Saturday, February 2, 2013 11:35:58 PM UTC-6, David Lynch wrote:

Thanks Dermot. I am not too worried about the layout stuff, although the wxFormBuilder seems to be abandoned, as it is not found on Sourceforge anymore. I was pretty happy with the Bind method description in the book, HOWEVER, I still can’t seem to find the master list of EVT_* events. How do I KNOW that EVT_BUTTON comes from a button click (in the controller class) but EVT_ENTER_WINDOW also comes from the mouse, but doesn’t propagate because it is not a command class event. How would I know if it wasn’t in the wxPython book? I’d like to see the complete list of events so I know what to bind in my handlers. Where are they in the source code even? I searched the source for them and couldn’t find a description of what they are or when they are triggered. Thanks again.

events = [e for e in dir(wx) if "EVT_" in e]
This only gets the main events. There are more in wx.grid for example.

Nevertheless a helpful command, thanks.

There's also the "Windows Styles and Events Hunter" app which is pretty helpful too. I wrote about it here: wxPython: Windows Styles and Events Hunter - Mouse Vs Python

When klicking on a widget in ./EventsInStyle.py it says:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line 14665, in <lambda>
    lambda event: event.callable(*event.args, **event.kw) )
  File "/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line 9771, in Refresh
    return _core_.Window_Refresh(*args, **kwargs)
TypeError: in method 'Window_Refresh', expected argument 1 of type 'wxWindow *'

···

Am 04.02.2013 22:25, schrieb Mike Driscoll:

--
Kurt Mueller

Hi Kurt,

···

On Wednesday, February 6, 2013 6:48:08 AM UTC-6, Kurt Müller wrote:

Am 04.02.2013 22:25, schrieb Mike Driscoll:

events = [e for e in dir(wx) if “EVT_” in e]

This only gets the main events. There are more in wx.grid for example.

Nevertheless a helpful command, thanks.

There’s also the “Windows Styles and Events Hunter” app which is pretty helpful too. I wrote about it here: http://www.blog.pythonlibrary.org/2011/07/25/wxpython-windows-styles-and-events-hunter/

When klicking on a widget in ./EventsInStyle.py it says:

Traceback (most recent call last):

File “/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py”, line 14665, in

lambda event: event.callable(*event.args, **[event.kw](http://event.kw)) )

File “/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py”, line 9771, in Refresh

return _core_.Window_Refresh(*args, **kwargs)

TypeError: in method ‘Window_Refresh’, expected argument 1 of type ‘wxWindow *’

I’ve never seen that one before. Hopefully the guy who wrote it can comment on that soon. He’s on this list.

  • Mike

Hi,
I have patched Andrea’s EventsInStyle.py to avoid the problem above

  • that it was pulsing a progress after it was deleted and the next
    problem that it was not finding any data because of a change in
    style in the web documents but as I am on linux I am hitting a
    problem because of the get system settings returning -1 to windows
    sizes - IF Kurt is on windows my patches should do for him and I can
    send him a zip file of it directly otherwise I am reluctant to push
    it anywhere but Andrea.
    Steve
···

On 15/02/13 20:10, Mike Driscoll wrote:

Hi Kurt,

  On Wednesday, February 6, 2013 6:48:08 AM UTC-6, Kurt Müller

wrote:

    Am

04.02.2013 22:25, schrieb Mike Driscoll:

    > events = [e for e in dir(wx) if "EVT_" in e]


    > This only gets the main events. There are more in wx.grid

for example.

    Nevertheless a helpful command, thanks.




    > There's also the "Windows Styles and Events Hunter" app

which is pretty helpful too. I wrote about it here: http://www.blog.pythonlibrary.org/2011/07/25/wxpython-windows-styles-and-events-hunter/

    When klicking on a widget in ./EventsInStyle.py it says:


    Traceback (most recent call last):


      File "/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/        wx/_core.py",

line 14665, in

        lambda event: event.callable(*event.args, **[event.kw](http://event.kw)        )

)

      File "/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/        wx/_core.py",

line 9771, in Refresh

        return _core_.Window_Refresh(*args, **kwargs)


    TypeError: in method 'Window_Refresh', expected argument 1 of

type ‘wxWindow *’

    I've never seen that one before. Hopefully the guy who wrote it

can comment on that soon. He’s on this list.

    - Mike

  You received this message because you are subscribed to the Google

Groups “wxPython-users” group.

  To unsubscribe from this group and stop receiving emails from it,

send an email to .
For more options, visit .


Steve Gadget Barnes

wxpython-users+unsubscribe@googlegroups.com
https://groups.google.com/groups/opt_out

Thanks for your info. I use wx.Python on SUSE 12.2.
So I think it is good to send the infos to Andrea Gavana.

Kurt

···

Am 16.02.2013 um 11:00 schrieb Steve Barnes:

On 15/02/13 20:10, Mike Driscoll wrote:

Hi Kurt,
On Wednesday, February 6, 2013 6:48:08 AM UTC-6, Kurt Müller wrote:
Am 04.02.2013 22:25, schrieb Mike Driscoll:
> events = [e for e in dir(wx) if "EVT_" in e]
> This only gets the main events. There are more in wx.grid for example.
Nevertheless a helpful command, thanks.

> There's also the "Windows Styles and Events Hunter" app which is pretty helpful too. I wrote about it here: wxPython: Windows Styles and Events Hunter - Mouse Vs Python
When klicking on a widget in ./EventsInStyle.py it says:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line 14665, in <lambda>
    lambda event: event.callable(*event.args, **event.kw) )
  File "/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line 9771, in Refresh
    return _core_.Window_Refresh(*args, **kwargs)
TypeError: in method 'Window_Refresh', expected argument 1 of type 'wxWindow *'
I've never seen that one before. Hopefully the guy who wrote it can comment on that soon. He's on this list.

I have patched Andrea's EventsInStyle.py to avoid the problem above - that it was pulsing a progress after it was deleted and the next problem that it was not finding any data because of a change in style in the web documents but as I am on linux I am hitting a problem because of the get system settings returning -1 to windows sizes - IF Kurt is on windows my patches should do for him and I can send him a zip file of it directly otherwise I am reluctant to push it anywhere but Andrea.

--
kurt.alfred.mueller@gmail.com

Thought you might be on linux of one flavour or another.
Steve

···

On 16/02/13 11:06, Kurt Mueller wrote:

Am 16.02.2013 um 11:00 schrieb Steve Barnes:
On 15/02/13 20:10, Mike Driscoll wrote:
Hi Kurt,
On Wednesday, February 6, 2013 6:48:08 AM UTC-6, Kurt Müller wrote:
Am 04.02.2013 22:25, schrieb Mike Driscoll:
events = [e for e in dir(wx) if "EVT_" in e] This only gets the main events. There are more in wx.grid for example.
Nevertheless a helpful command, thanks.
There's also the "Windows Styles and Events Hunter" app which is pretty helpful too. I wrote about it here:
  When klicking on a widget in ./EventsInStyle.py it says: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line 14665, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) File "/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line 9771, in Refresh return _core_.Window_Refresh(*args, **kwargs) TypeError: in method 'Window_Refresh', expected argument 1 of type 'wxWindow *' I've never seen that one before. Hopefully the guy who wrote it can comment on that soon. He's on this list.

I have patched Andrea's EventsInStyle.py to avoid the problem above - that it was pulsing a progress after it was deleted and the next problem that it was not finding any data because of a change in style in the web documents but as I am on linux I am hitting a problem because of the get system settings returning -1 to windows sizes - IF Kurt is on windows my patches should do for him and I can send him a zip file of it directly otherwise I am reluctant to push it anywhere but Andrea.


Thanks for your info. I use wx.Python on SUSE 12.2.
So I think it is good to send the infos to Andrea Gavana.
Kurt


Steve Gadget Barnes

http://www.blog.pythonlibrary.org/2011/07/25/wxpython-windows-styles-and-events-hunter/

Hi Steve,

Hi Kurt,

> events = [e for e in dir(wx) if "EVT_" in e]
> This only gets the main events. There are more in wx.grid for example.
Nevertheless a helpful command, thanks.

> There's also the "Windows Styles and Events Hunter" app which is pretty
> helpful too. I wrote about it here:
> wxPython: Windows Styles and Events Hunter - Mouse Vs Python
When klicking on a widget in ./EventsInStyle.py it says:
Traceback (most recent call last):
  File
"/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line
14665, in <lambda>
    lambda event: event.callable(*event.args, **event.kw) )
  File
"/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line
9771, in Refresh
    return _core_.Window_Refresh(*args, **kwargs)
TypeError: in method 'Window_Refresh', expected argument 1 of type
'wxWindow *'

I've never seen that one before. Hopefully the guy who wrote it can comment
on that soon. He's on this list.

- Mike
--
You received this message because you are subscribed to the Google Groups
"wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi,

I have patched Andrea's EventsInStyle.py to avoid the problem above - that
it was pulsing a progress after it was deleted and the next problem that it
was not finding any data because of a change in style in the web documents
but as I am on linux I am hitting a problem because of the get system
settings returning -1 to windows sizes - IF Kurt is on windows my patches
should do for him and I can send him a zip file of it directly otherwise I
am reluctant to push it anywhere but Andrea.

Please do send me your patch, I'll update EventsInStyle. I will also
need to patch the wxPython demo as most of EventsInStyle went into it
as well, even though it is not switched on by default.

Thank you!

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."

# ------------------------------------------------------------- #
def ask_mailing_list_support(email):

    if mention_platform_and_version() and include_sample_app():
        send_message(email)
    else:
        install_malware()
        erase_hard_drives()
# ------------------------------------------------------------- #

···

On 16 February 2013 11:00, Steve Barnes wrote:

On 15/02/13 20:10, Mike Driscoll wrote:
On Wednesday, February 6, 2013 6:48:08 AM UTC-6, Kurt Müller wrote:

Am 04.02.2013 22:25, schrieb Mike Driscoll:

Reply with attachment sent directly to Andrea.

···

On 16/02/13 16:20, Andrea Gavana wrote:


Hi Steve,
On 16 February 2013 11:00, Steve Barnes wrote:

On 15/02/13 20:10, Mike Driscoll wrote:
Hi Kurt,
On Wednesday, February 6, 2013 6:48:08 AM UTC-6, Kurt Müller wrote:
Am 04.02.2013 22:25, schrieb Mike Driscoll:
events = [e for e in dir(wx) if "EVT_" in e]
This only gets the main events. There are more in wx.grid for example.
Nevertheless a helpful command, thanks.
There's also the "Windows Styles and Events Hunter" app which is pretty
helpful too. I wrote about it here:
  When klicking on a widget in ./EventsInStyle.py it says:
Traceback (most recent call last):
File
"/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line
14665, in <lambda>
lambda event: event.callable(*event.args, **event.kw) )
File
"/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line
9771, in Refresh
return _core_.Window_Refresh(*args, **kwargs)
TypeError: in method 'Window_Refresh', expected argument 1 of type
'wxWindow *'

I've never seen that one before. Hopefully the guy who wrote it can comment
on that soon. He's on this list.
- Mike
--
You received this message because you are subscribed to the Google Groups
"wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to .
For more options, visit .
Hi,
I have patched Andrea's EventsInStyle.py to avoid the problem above - that
it was pulsing a progress after it was deleted and the next problem that it
was not finding any data because of a change in style in the web documents
but as I am on linux I am hitting a problem because of the get system
settings returning -1 to windows sizes - IF Kurt is on windows my patches
should do for him and I can send him a zip file of it directly otherwise I
am reluctant to push it anywhere but Andrea.

Please do send me your patch, I'll update EventsInStyle. I will also
need to patch the wxPython demo as most of EventsInStyle went into it
as well, even though it is not switched on by default.
Thank you!
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
# ------------------------------------------------------------- #
def ask_mailing_list_support(email):
if mention_platform_and_version() and include_sample_app():
send_message(email)
else:
install_malware()
erase_hard_drives()
# ------------------------------------------------------------- #


Steve Gadget Barnes

http://www.blog.pythonlibrary.org/2011/07/25/wxpython-windows-styles-and-events-hunter/wxpython-users+unsubscribe@googlegroups.comhttps://groups.google.com/groups/opt_outhttp://www.infinity77.net

Unfortunately Steve has patched a very old version of EventsInstyle.py
(probably coming from Mike's website). I have integrated Steve's
changes into the recent version of the tool, and it is available here:

http://xoomer.virgilio.it/infinity77/Zipped/EventsInStyle.py

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."

···

On 16 February 2013 17:32, Steve Barnes wrote:

On 16/02/13 16:20, Andrea Gavana wrote:

Hi Steve,

On 16 February 2013 11:00, Steve Barnes wrote:

On 15/02/13 20:10, Mike Driscoll wrote:

Hi Kurt,

On Wednesday, February 6, 2013 6:48:08 AM UTC-6, Kurt Müller wrote:

Am 04.02.2013 22:25, schrieb Mike Driscoll:

events = [e for e in dir(wx) if "EVT_" in e]
This only gets the main events. There are more in wx.grid for example.

Nevertheless a helpful command, thanks.

There's also the "Windows Styles and Events Hunter" app which is pretty
helpful too. I wrote about it here:
wxPython: Windows Styles and Events Hunter - Mouse Vs Python

When klicking on a widget in ./EventsInStyle.py it says:
Traceback (most recent call last):
  File
"/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line
14665, in <lambda>
    lambda event: event.callable(*event.args, **event.kw) )
  File
"/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line
9771, in Refresh
    return _core_.Window_Refresh(*args, **kwargs)
TypeError: in method 'Window_Refresh', expected argument 1 of type
'wxWindow *'

I've never seen that one before. Hopefully the guy who wrote it can comment
on that soon. He's on this list.

- Mike
--
You received this message because you are subscribed to the Google Groups
"wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi,

I have patched Andrea's EventsInStyle.py to avoid the problem above - that
it was pulsing a progress after it was deleted and the next problem that it
was not finding any data because of a change in style in the web documents
but as I am on linux I am hitting a problem because of the get system
settings returning -1 to windows sizes - IF Kurt is on windows my patches
should do for him and I can send him a zip file of it directly otherwise I
am reluctant to push it anywhere but Andrea.

Please do send me your patch, I'll update EventsInStyle. I will also
need to patch the wxPython demo as most of EventsInStyle went into it
as well, even though it is not switched on by default.

Thank you!

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."
http://www.infinity77.net

Andrea,
Thanks for the prompt action and apologies for the use of the old
script. I have tried your updated script with ‘2.8.12.1
(gtk2-unicode)’/Python 2.7.3/Ubuntu 12.10 and it works well but with
wxPython 2.9.4.1 it hangs once it gets some data to display - I
suspect because of the wrapping issue I mentioned - I have not had
time to check yet.
Steve

···

On 17/02/13 23:41, Andrea Gavana wrote:

On 16 February 2013 17:32, Steve Barnes wrote:

On 16/02/13 16:20, Andrea Gavana wrote:
Hi Steve,
On 16 February 2013 11:00, Steve Barnes wrote:
On 15/02/13 20:10, Mike Driscoll wrote:
Hi Kurt,
On Wednesday, February 6, 2013 6:48:08 AM UTC-6, Kurt Müller wrote:
Am 04.02.2013 22:25, schrieb Mike Driscoll:
events = [e for e in dir(wx) if "EVT_" in e]
This only gets the main events. There are more in wx.grid for example.
Nevertheless a helpful command, thanks.
There's also the "Windows Styles and Events Hunter" app which is pretty
helpful too. I wrote about it here:
When klicking on a widget in ./EventsInStyle.py it says:
Traceback (most recent call last):
File
"/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line
14665, in <lambda>
lambda event: event.callable(*event.args, **event.kw) )
File
"/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode/wx/_core.py", line
9771, in Refresh
return _core_.Window_Refresh(*args, **kwargs)
TypeError: in method 'Window_Refresh', expected argument 1 of type
'wxWindow *'
I've never seen that one before. Hopefully the guy who wrote it can comment
on that soon. He's on this list.
- Mike
--
You received this message because you are subscribed to the Google Groups
"wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to .
For more options, visit .
Hi,
I have patched Andrea's EventsInStyle.py to avoid the problem above - that
it was pulsing a progress after it was deleted and the next problem that it
was not finding any data because of a change in style in the web documents
but as I am on linux I am hitting a problem because of the get system
settings returning -1 to windows sizes - IF Kurt is on windows my patches
should do for him and I can send him a zip file of it directly otherwise I
am reluctant to push it anywhere but Andrea.
Please do send me your patch, I'll update EventsInStyle. I will also
need to patch the wxPython demo as most of EventsInStyle went into it
as well, even though it is not switched on by default.
Thank you!
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."



Unfortunately Steve has patched a very old version of EventsInstyle.py
(probably coming from Mike's website). I have integrated Steve's
changes into the recent version of the tool, and it is available here:
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."


Steve Gadget Barnes

http://www.blog.pythonlibrary.org/2011/07/25/wxpython-windows-styles-and-events-hunter/wxpython-users+unsubscribe@googlegroups.comhttps://groups.google.com/groups/opt_outhttp://www.infinity77.nethttp://xoomer.virgilio.it/infinity77/Zipped/EventsInStyle.pyhttp://www.infinity77.net

Hi,

I have patched Andrea’s EventsInStyle.py to avoid the problem above - that

it was pulsing a progress after it was deleted and the next problem that it

was not finding any data because of a change in style in the web documents

but as I am on linux I am hitting a problem because of the get system

settings returning -1 to windows sizes - IF Kurt is on windows my patches

should do for him and I can send him a zip file of it directly otherwise I

am reluctant to push it anywhere but Andrea.

Please do send me your patch, I’ll update EventsInStyle. I will also

need to patch the wxPython demo as most of EventsInStyle went into it

as well, even though it is not switched on by default.

Thank you!

Andrea.

“Imagination Is The Only Weapon In The War Against Reality.”

http://www.infinity77.net

Unfortunately Steve has patched a very old version of EventsInstyle.py

(probably coming from Mike’s website). I have integrated Steve’s

changes into the recent version of the tool, and it is available here:

http://xoomer.virgilio.it/infinity77/Zipped/EventsInStyle.py

Andrea.

“Imagination Is The Only Weapon In The War Against Reality.”

http://www.infinity77.net

Oops. Sorry about that. I fixed my article to include a link to the most current version of the script.

  • Mike