[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-bugs] <bug>: <user did not comment on bug report>

From: Karsten Hilbert
Subject: Re: [Gnumed-bugs] <bug>: <user did not comment on bug report>
Date: Sun, 5 Feb 2012 19:21:06 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

Hello Andzrej,

thanks for your report.

> client version: 1.1.10


> 2012-02-05 15:17:56  DEBUG     gm.gui 
> (c:\workplace\gnumed-client.1.1.10\build\pyi.win32\gnumed\outpyz1.pyz\gnumed.wxpython.gmexceptionhandlingwidgets::handle_uncaught_exception_wx()
>  #189): unhandled exception caught:
> Traceback (most recent call last):
>   File 
> "C:\workplace\gnumed-client.1.1.10\build\pyi.win32\gnumed\outPYZ1.pyz\Gnumed.wxpython.gmGuiMain",
>  line 2294, in __on_unblock_cursor

This function is only intended to be used when the cursor is
"wedged", that is when it displays the icon for "busy" but
GNUmed is not actually busy. It seems you invoked this
function from the menu when it wasn't actually necessary.

>   File 
> "C:\workplace\gnumed-client.1.1.10\build\pyi.win32\gnumed\outPYZ1.pyz\wx._misc",
>  line 319, in EndBusyCursor
> PyAssertionError: C++ assertion "gs_wxBusyCursorCount > 0" failed at 
> ..\..\src\msw\utilsgui.cpp(178) in wxEndBusyCursor(): no matching 
> wxBeginBusyCursor() for wxEndBusyCursor()

Windows, however, cannot deal with wxEndBusyCursor() being
called when it is not *absolutely* necessary. It helpfully
tells us that it shouldn't be necessary. Giving that helpful
hint makes wxWidgets on Windows choke such that it dies
(throws an exception).

This should be better with 1.1.11 which we released recently.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]