Bug #605: Audacious starts up with visible artifacts - Audacious - OLD, PLEASE USE GITHUB DISCUSSIONS/ISSUES - Redmine

Bug #605

Audacious starts up with visible artifacts

Added by Davyd McColl almost 9 years ago. Updated almost 9 years ago.

Status:

Closed

Priority:

Minor

Assignee:

Category:

win32

Target version:

3.7.1

Start date:

December 15, 2015

Due date:

% Done:

100%

Estimated time:

Affects version:

3.7

Description

When Audacious starts up on Windows, using the classic skins, I see artifacts on-screen. This only applies when the player remembers a prior shaded state. Please see attached screenshot -- I don't think I'm explaining it well. Applies to latest download at time of writing (3.7.2)

audacious-startup.png (6.82 KB) audacious-startup.png		Davyd McColl, December 15, 2015 11:17
libgdk-win32-2.0-0.dll (672 KB) libgdk-win32-2.0-0.dll		John Lindgren, December 24, 2015 12:37

History

#1 Updated by John Lindgren almost 9 years ago

Target version deleted (~~3.7.1~~)
Affects version 3.7 added
Affects version deleted (~~3.7.1~~)

It appears to be a bug in GTK+ on Windows. If you find a fix, I'd be happy to include it. Otherwise, this will eventually be fixed by the Qt port.

Also, please stop talking about versions that don't exist. 3.7 is the newest. There is no 3.7.1 or 3.7.2 yet.

#2 Updated by Davyd McColl almost 9 years ago

Also, please stop talking about versions that don't exist. 3.7 is the newest. There is no 3.7.1 or 3.7.2 yet.

Apologies -- I keep on getting muddled between the 3.6.x releases and 3.7 ):

I will try to build on Windows at some point -- I'd love to be more than just a bug reporter. I'm not a GTK guru though, so I wouldn't hold my breath for a useful patch from me ):

#3 Updated by John Lindgren almost 9 years ago

I looked into this further and it appears to be actually due to a bug/undocumented feature of the Win32 API function SetWindowPos. Incidentally, the problem isn't reproducible under Wine, only actual Windows. It's possible to work around it in GTK+. I'm attaching a patched DLL which fixes the problem for me.