Re: gtk treeview windows



Oh, sorry. I assume you have verified that you don't have any heap
corruption by running the code under valgrind on Linux? Other than
that I really can't give any specific advice. Perhaps ask somebody
else to read the code carefully. If the problem did not occur at some
earlier stage, then you could do a binary search through your version
history to find the exact changes that made the problems occur. But if
the problem happens very randomly and rarely, of course that is going
to be tedious, as you can never be sure if one version really is
clean, or if the problem just happens not to occur when you test that
version.

--tml

I still think maybe we're missing each other here. The problem has
never occurred on linux, and the software has run there for several
years, so heap corruption seems unlikely. The problem occurs only on
Windows, and only with the libwimp theme engine. We don't have any
previous versions that worked correctly as this is our first porting
attempt.

What I have done:

Added debugging message code to the test-collapse-row and
test-expand-row signals. As expected these fire correctly when the
treeview is working properly, but they do not fire when the treeview
is locked up. However, using the arrow keys to navigate the treeview,
these signals fire correctly.

We are also connected to the button-release-event for the treeview.
This only fires when clicking on the row, not the button (little plus
symbol) that would expand or collapse the treeview row.

What I would like to know is if there is a signal, or some way I can
detect whether the button is receiving the mouse click, but not
expanding for some reason, or where exactly the problem is occurring.

Matthew



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