wxPython - drawing without paint event

[Matt Bitten]

I've got a wxPython program that needs to do some drawing on a DC on a
regular basis, whether or not a paint event happens. I know how to
make a ClientDC to do the drawing in, and I know what drawing calls to
make. But how do I make it all happen? After I call MainLoop, none of
my code gets called unless there is an event. And there is no event,
so my code doesn't get called. What do I do?

[7stud]

On Aug 9, 7:46 pm, Matt Bitten <mbitte...@yaho o.comwrote:

I've got a wxPython program that needs to do some drawing on a DC on a
regular basis.... And there is no event,
so my code doesn't get called. What do I do?

Then the event is: "on a regular basis", i.e. the passage of time.
You can use a wx.Timer to create events at regular intervals, which
your code can respond to:

-------
import wx

class MyFrame(wx.Fram e):
def __init__(self):
wx.Frame.__init __(self, None, -1, "My Window")

panel = wx.Panel(self, -1)
self.text = wx.StaticText(p anel, -1, "hello", pos=(40, 40) )

self.timer = wx.Timer(self)
self.Bind(wx.EV T_TIMER, self.on_timer_e vent)
self.timer.Star t(milliseconds= 1000, oneShot=False)

def on_timer_event( self, event):
if self.text.GetLa bel() == "hello":
self.text.SetLa bel("goodbye")
else:
self.text.SetLa bel("hello")
app = wx.App(redirect =False)

win = MyFrame()
win.Show()

app.MainLoop()
----------------

Make sure you save the timer in self so that you have a permanent
reference to the object, otherwise the timer will be destroyed when
__init_ returns.

[glenn.chappell]

On Aug 10, 1:40 am, 7stud <bbxx789_0...@y ahoo.comwrote:

On Aug 9, 7:46 pm, Matt Bitten <mbitte...@yaho o.comwrote:

I've got a wxPython program that needs to do some drawing on a DC on a
regular basis.... And there is no event,
so my code doesn't get called. What do I do?

Then the event is: "on a regular basis", i.e. the passage of time.
You can use a wx.Timer to create events at regular intervals, which
your code can respond to:
...

Thanks!

On a related topic, it seems like it would be nice to do *all* drawing
in
response to paint events. When I get an event from the timer, I would
just tell wx that part of the window needs redrawing, and depend on it
to give me a paint even when nothing of higher priority needs to be
done.
I've seen this kind of logic recommended in other GUI tookits. Is it a
good idea in wxPython, and, if so, how does one do it?

[Bjoern Schliessmann]

gl************@ gmail.com wrote:

On a related topic, it seems like it would be nice to do *all*
drawing in
response to paint events. When I get an event from the timer, I
would just tell wx that part of the window needs redrawing, and
depend on it to give me a paint even when nothing of higher
priority needs to be done.
I've seen this kind of logic recommended in other GUI tookits. Is
it a good idea in wxPython, and, if so, how does one do it?

At least it is not required -- there are device contexts for use
inside and outside of paint events.

One nice strategy from an example in "wxPython in Action" is the
following:

* the frame has Draw methods that draw into a BufferedDC, which is
chained to a bitmap member

* inside the paint method, the bitmap member is drawn to screen

Regards,
Björn

--
BOFH excuse #393:

Interference from the Van Allen Belt.

[glenn.chappell]

On Aug 11, 3:31 am, Bjoern Schliessmann <usenet-
mail-0306.20.chr0n.. .@spamgourmet.c omwrote:

glenn.chapp...@ gmail.com wrote:

On a related topic, it seems like it would be nice to do *all*
drawing in
response topaintevents. When I get aneventfrom the timer, I
would just tell wx that part of the window needs redrawing, and
depend on it to give me apainteven when nothing of higher
priority needs to be done.

One nice strategy from an example in "wxPython in Action" is the
following:

* the frame has Draw methods that draw into a BufferedDC, which is
chained to a bitmap member

* inside thepaintmethod, the bitmap member is drawn to screen

Okay, but how do I tell wx that it needs to send me a paint event?

[7stud]

On Aug 11, 7:59 pm, glenn.chapp...@ gmail.com wrote:

On Aug 11, 3:31 am, Bjoern Schliessmann <usenet-

mail-0306.20.chr0n.. .@spamgourmet.c omwrote:

glenn.chapp...@ gmail.com wrote:

On a related topic, it seems like it would be nice to do *all*
drawing in
response topaintevents. When I get aneventfrom the timer, I
would just tell wx that part of the window needs redrawing, and
depend on it to give me apainteven when nothing of higher
priority needs to be done.

One nice strategy from an example in "wxPython in Action" is the
following:

* the frame has Draw methods that draw into a BufferedDC, which is
chained to a bitmap member

* inside thepaintmethod, the bitmap member is drawn to screen

Okay, but how do I tell wx that it needs to send me a paint event?

Try this:

--------------
import wx

class MyFrame(wx.Fram e):
def __init__(self):
wx.Frame.__init __(self, None, -1, "My Window")

panel = wx.Panel(self, -1)
self.text = wx.StaticText(p anel, -1, "hello", pos=(40, 40) )

self.timer = wx.Timer(self)
self.Bind(wx.EV T_TIMER, self.on_timer_e vent)
self.timer.Star t(milliseconds= 1000, oneShot=False)

self.Bind(wx.EV T_PAINT, self.on_paint)

def on_timer_event( self, event):
self.GetEventHa ndler().Process Event(wx.PaintE vent())

def on_paint(self, event):
print "execution entered on_paint"

app = wx.App(redirect =False)

win = MyFrame()
win.Show()

app.MainLoop()
------------

I'm not sure why the call should be
self.GetEventHa ndler().Process Event() instead of just
self.ProcessEve nt().

[Bjoern Schliessmann]

gl************@ gmail.com wrote:

Okay, but how do I tell wx that it needs to send me a paint event?

It will send it on its own. You just need to bind your OnPaint (or
similar) method to it like 7stud demonstrates.

I really recommend reading "wxPython in Action", or at least the
tutorial.

Regards,
Björn

--
BOFH excuse #273:

The cord jumped over and hit the power switch.

[7stud]

On Aug 12, 6:06 am, Bjoern Schliessmann <usenet-
mail-0306.20.chr0n.. .@spamgourmet.c omwrote:

I really recommend reading "wxPython in Action", or at least the
tutorial.

I don't. "wxPython in Action" is by far the worst computer book I've
ever purchased. It's poorly organized, poorly written, and full of
mistakes--and it's expensive. The fact that the authors foist that
piece of junk on unsuspecting newbies is a crime.

[7stud]

On Aug 12, 2:20 pm, Bjoern Schliessmann <usenet-
mail-0306.20.chr0n.. .@spamgourmet.c omwrote:

But any suggestions what's
better for a beginner? The (incomplete) tutorial surely not.

Another GUI toolkit.

[Bjoern Schliessmann]

7stud wrote:

On Aug 12, 2:20 pm, Bjoern Schliessmann <usenet-

>But any suggestions what's
better for a beginner? The (incomplete) tutorial surely not.

Another GUI toolkit.

So it seems your dislike is not for the book, but for the toolkit.

Regards,
Björn

--
BOFH excuse #414:

tachyon emissions overloading the system