That depends on what you mean. Your application cannot write to memory
outside of your process. However, you can certainly trash your own
process' address space. By default, a memory DC has a 1x1 monochrome
bitmap associated with it. If you write a bunch of stuff, you will (of
course) write outside of that bitmap. That can cause your process to go
squirrelly, but it shouldn't have any impact on the rest of the system.
···
On Thu, 13 Sep 2007 09:49:26 -0400, Bob Klahn <bobklahn@comcast.net> wrote:
I've been using wx.MemoryDC for a few days now. But when I first
started using it, I failed to associate a bitmap with it properly.
wxPython did not issue any warnings, and my code actually did what it
was supposed to do.But my PC suddenly began acting strangely, requiring multiple
reboots. I finally discovered and fixed my bitmap/wx.MemoryDC
association error, and ... my PC stopped acting strangely.So my question is: Is it really possible for wx.MemoryDC to write to
supposedly protected memory? A few days of circumstantial evidence
suggest that it is, and that bothers me. Or was this simply a
multi-day coincidence?
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.