Discussion:
Rebuilding with latest wx?
Cees de Groot
2006-07-19 15:18:01 UTC
Permalink
Hi all (well... both of you, it seems ;))

The biggest issue that we have right now is that the wait cursor thingy
doesn't show up. We had a usability lab yesterday (the first one, small
scale, but you have to start somewhere) and this was quite a major issue.

As this seems to be a wx problem, I'm tempted to try and recompile a later
wx version. I haven't tracked wx closely (well... not at all, actually),
so my question is: would that be a feasible job?

Apart from that, the app is holding up pretty well. Lots of notes from the
usability lab, of course, but it looks stable enough for production use.
The only other issue I'm currently aware of is that when you set a new
image in a tree, it doesn't get updated (minor stuff, really, but feedback
is oh so important - this app is going to be used by people interested in
national history, which means the users are bound to be elderly men with
marginal PC experience...)
Rob Gayvert
2006-07-19 15:18:01 UTC
Permalink
Post by Cees de Groot
Hi all (well... both of you, it seems ;))
The biggest issue that we have right now is that the wait cursor
thingy doesn't show up. We had a usability lab yesterday (the first
one, small scale, but you have to start somewhere) and this was quite
a major issue.
As this seems to be a wx problem, I'm tempted to try and recompile a
later wx version. I haven't tracked wx closely (well... not at all,
actually), so my question is: would that be a feasible job?
Apart from that, the app is holding up pretty well. Lots of notes from
the usability lab, of course, but it looks stable enough for
production use. The only other issue I'm currently aware of is that
when you set a new image in a tree, it doesn't get updated (minor
stuff, really, but feedback is oh so important - this app is going to
be used by people interested in national history, which means the
users are bound to be elderly men with marginal PC experience...)
Cees,

I think the problem is in wxWindowMSW::HandleSetCursor, which claims to
set the busy cursor if wxIsBusy(), but doesn't in the case of a grid.
Try changing

if ( !processedEvtSetCursor && m_cursor.Ok() )
{
hcursor = GetHcursorOf(m_cursor);
}

to

if (isBusy)
{
hcursor = wxGetCurrentBusyCursor();
}
else if ( !processedEvtSetCursor && m_cursor.Ok() )
{
hcursor = GetHcursorOf(m_cursor);
}

I'm not sure what all is going on with processedEvtSetCursor, but this
patch seems to make the busy cursor stick, at least in my simple test case.

.. Rob

Loading...