After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 667415 - GtkCellRendererText: Interpret "" color proprerties like NULL
GtkCellRendererText: Interpret "" color proprerties like NULL
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
3.1.x
Other Linux
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2012-01-06 15:26 UTC by Murray Cumming
Modified: 2018-02-10 04:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
0001-GtkCellRendererText-Interpret-color-properties-like-.patch (2.20 KB, patch)
2012-01-06 15:26 UTC, Murray Cumming 		none Details | Review

Description Murray Cumming 2012-01-06 15:26:53 UTC 
Created attachment 204752 [details] [review]
0001-GtkCellRendererText-Interpret-color-properties-like-.patch

This patch lets this work in gtkmm code:
  cell.property_foreground() = "";
or
  cell.property_foreground() = std::string();
or
  cell.property_foreground() = Glib::ustring();
to
  reset the foreground color to the default.

This is not possible in gtkmm, which does not generally distinguish between NULL (0) and "":
  cell.property_foreground() = 0;
Comment 1 Murray Cumming 2012-06-08 14:35:28 UTC 
Please?
Comment 2 Matthias Clasen 2012-06-09 01:14:19 UTC 
NULL and "" are two very different things.
I guess we'll have to agree to disagree on that point.
Comment 3 Murray Cumming 2012-06-09 08:49:59 UTC 
OK. I'm not very interested in arguing about it generally. But can you tell me what the difference is in this case?

Or, to put it another way, what is the advantage of interpreting "" as an invalid color instead of just interpreting it as an unset, like NULL.
Comment 4 Matthias Clasen 2018-02-10 04:39:14 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.