On Wed, Aug 5, 2009 at 4:46 PM, Jürgen Spitzmüller wrote:
> Well, at least I have it installed, and I played a bit with it in the past. To
> me, it looks interesting and useful, especially since there is a German GC
> available. So I am a potential user.
I have found another regression in 1.6; now
John McCabe-Dansted wrote:
> The patch relies on the fact that the the ErrorList dialog is only
> updated before it is shown. Thus we can safely prevent updateContents
> from regenerating the list of errors unless showEvent has been called.
> Regenerating the list of Errors is problematic because A
On Tue, Aug 4, 2009 at 10:30 PM, Jürgen Spitzmüller wrote:
> John McCabe-Dansted wrote:
>> Attached is a patch that does (2).
>
> I admit that I do not really understand what you are doing with the patch.
The patch relies on the fact that the the ErrorList dialog is only
updated before it is shown
John McCabe-Dansted wrote:
> Attached is a patch that does (2).
I admit that I do not really understand what you are doing with the patch.
Jürgen
OK, I noticed a problem in the last patch. It would cause the error in
the ErrorListDialog to become unhighlighted when clicking on the main
window.
The root cause of the problem appears to be that GuiDialog::updateView
calls updateContents, which causes ErrorListDialog to reread all the
error eac
How does this patch look? I thought it would be cleaner if I could
avoid needing to add the variable "bool need_to_set_row", however I
cannot see how this could be done. If I put setCurrentRow(0) in
GuiErrorList::showEvent it doesn't do anything, and calling
setCurrentRow(0) on every update was the
