Update. The crash only seems to occur when restoring takes place through the double-click action.
John Hoffman wrote:
I recently upgraded to 2.5.1.5, and it seemed to work transparently. Unfortunately, I received reports from users and discovered that on minimizing to the tray and restoring I received the error that there was an "unhandled exception". The Event Viewer shows no details about the problem.
Does the demo do it too? (Mine doesn't) Which platform does this happen on?
Well, I fixed my own problem and possibly made my program more efficient by using a static wxTaskBarIcon and turning it on and off using SetIcon()/RemoveIcon(), but it looks like the ability to delete a taskbar icon is somewhat broken, and still ought to be repaired...
Well, I fixed my own problem and possibly made my program more efficient by using a static wxTaskBarIcon and turning it on and off using SetIcon()/RemoveIcon(), but it looks like the ability to delete a taskbar icon is somewhat broken, and still ought to be repaired...
wxTaskbarIcon breaks the wxPython mold and has the actual destructor wrapped by __del__ (because it is not owned by anything else) so the proper way to destroy it is to del all references to it. I'll fix Destroy() so it is a no-op for that class.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Well, I fixed my own problem and possibly made my program more efficient by using a static wxTaskBarIcon and turning it on and off using SetIcon()/RemoveIcon(), but it looks like the ability to delete a taskbar icon is somewhat broken, and still ought to be repaired...
wxTaskbarIcon breaks the wxPython mold and has the actual destructor wrapped by __del__ (because it is not owned by anything else) so the proper way to destroy it is to del all references to it. I'll fix Destroy() so it is a no-op for that class.
Make it do a RemoveIcon(), that'd match the behavior for pre-2.5.