While generically a wx.Event can be generated both by user actions(e.g., resize of a wx.Window) and by calls to functions (e.g.,wx.Window.SetSize), wxPython controls normally send wx.CommandEvent -derived events only for the user-generatedevents. The only exceptions to this rule are:
WxPython In Action
Hello,
according to the book "wxPython in action", i can repaint my wx.grid by
using forceRefresh() after changes in the wx.gridtablebase class. But
actually this has no effect at all (at least i can't see one).
jakob fischer wrote:
> Hello,
> according to the book "wxPython in action", i can repaint my wx.grid by
> using forceRefresh() after changes in the wx.gridtablebase class. But
> actually this has no effect at all (at least i can't see one).
I'm very new to wxpython. I wanted to create a gui app which takes
input from the user in the first page and pressing 'Next' takes them
to the next page. For the first page, i created a frame and added all
the needed stuff (referring the book wxpython-in-action) like the
fields, buttons, dropdowns etc..
> I'm very new to wxpython. I wanted to create a gui app which takes
> input from the user in the first page and pressing 'Next' takes them
> to the next page. For the first page, i created a frame and added all
> the needed stuff (referring the book wxpython-in-action) like the
> fields, buttons, dropdowns etc..
I wrote a tutorial on notebooks over the last couple of days, so you
can read that if you like (see link for my blog below). The wiki is
also a good place to learn and I also recommend googling for the
zetcode wxpython tutorial.
Maybe if you give more details on your issues with wxpython I can provide more specific help to ease your pain with that api, there is no helping with kicad api though Not until the new stable python interface.
38c6e68cf9