Bob Klahn 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?
I wouldn't expect so, but you never can tell with Microsoft.
A few days of circumstantial evidence suggest that it is, and that bothers me. Or was this simply a multi-day coincidence?
Can you duplicate the problem on any other PC? (Especially a clean install of Windows.) If so then I'd blame wx.MemoryDC in one way or another, but if not then it was most likely a coincidence.
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!