1.4rc2: delayed redraw of 3d app

[Fred2]

Since 1.4rc2, Google SketchUp does not immediately redraw the 3d drawing area, but only after the view has been invalidated another time.
That means SketchUp starts with black screen until you force it to update the view (by moving, resizing the window or orbiting or panning the view). This is also noticeable when you click, double-click or triple-click an object in order to select it: The object is not immediately highlighted although it is selected.

[Christoph Korn]

This sounds like a regression.
In case the bug has not yet been posted [1] you can run a regression test
using git [2]. It is rather simple. Just ask if you run into troubles.

[1] http://bugs.winehq.org/buglist.cgi?quic ... t_id=30649
[2] http://wiki.winehq.org/RegressionTesting

Am 11.02.2012 15:16, schrieb Fred2:

Since 1.4rc2, Google SketchUp does not immediately redraw the 3d drawing area, but only after the view has been invalidated another time.
That means SketchUp starts with black screen until you force it to update the view (by moving, resizing the window or orbiting or panning the view). This is also noticeable when you click, double-click or triple-click an object in order to select it: The object is not immediately highlighted although it is selected.

[Fred2]

I'm not sure if I did it right. I started to bisect between wine-1.4-rc1 (good) and wine-1.4-rc2 (bad). Since the first bisect showed the error, I moved towards rc1 until the first commit ("Release 1.4-rc2", it's a release, so are there any changes that could have introduced the error?).

I then tried again between rc1 and 1.3.37 and everything worked.

[dimesio]

Since the first bisect showed the error, I moved towards rc1 until the first commit ("Release 1.4-rc2", it's

The version tag could not be the cause of a regression, and what you said does not even make sense: if all the bisects were bad between 1.4-rc1 and 1.4-rc2, then the result would have been 1.4-rc1, not 1.4-rc2. Clearly you did something wrong.