Bug 945 - GTK# doesnt show background colors at widgets
Summary: GTK# doesnt show background colors at widgets
Alias: None
Product: Gtk#
Classification: Mono
Component: gtk-sharp ()
Version: 2.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-09-20 17:34 UTC by Ondřej Profant
Modified: 2011-10-12 19:12 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Ondřej Profant 2011-09-20 17:34:44 UTC
I would have red button (for example). On Linux I use somethink like:

button1.ModifyBg( StateType.Normal, new Gdk.Color(255,0,0) );

and button has normal statetype and red background, but on Windows 7 (both, 32 and 64bit) this command has no efect. Other color options (ModifyFg) also do not work.
Comment 1 Mike Kestner 2011-10-12 19:12:59 UTC
This is almost certainly a gtk+ windows port issue.  The method you mention is identical on the two platforms from a binding standpoint, which means it's the underlying native code that's most likely not doing what you expect.

You could ask on gtk-app-devel-list perhaps if this is supposed to be supported on windows or if it's a known issue, to determine whether it should be filed against gtk+.  They probably won't want to fix it in anything but 3.x at this point though.