ruby-****@sourc*****
ruby-****@sourc*****
2012年 9月 23日 (日) 08:34:04 JST
-------------------------
REMOTE_ADDR = 184.145.80.187
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-treev-trees
-------------------------
@@ -271,7 +271,7 @@
Before we delve too deep into the mechanics of dealing with and programming the tree view cell rendering, we need to mention that many times certain cells in a tree view need to be presented differently than the rest of them. Perhaps, most of the data needs simply to be rendered as active and displayed normally with no adornments, while some cells need to be exposed or highlighted and others again may need to be shaded or disabled in the tree view. In such situations this inevitably reveals a tighter than usual relationship between the model and the view. We have already seen evidence of this on previous page in the paragraph entitled "((<Dissecting the column creation|tut-gtk2-treev-parts#Dissecting the column creation>))" when discussing the hash parameter for cell-renderer's attributes where attributes were passed to Gtk::TreeViewColumn object's constructor and to the "set_attribute" and "set_attributes" instance methods, as a set of name/value pairs, for whose values we
were adamantly insisting were not the values of these very attributes but rather the column numbers of their respective values in the model.
:Reminder:
- Let us remind ourselves how did the code with these hash arguments looked like:
+ Not that earlier mentioned "tighter relationship between tree view and the model" is directly related to "set_cell_data_func", it (namely the tighter relationship between the tree model an view) is very often exploited inside the associated code block of cell data function. So let us remind ourselves how these hash arguments looked like, and in what context were they used:
column = Gtk::TreeViewColumn.new("Buy", renderer, {"text" => BUY_IT, :foreground => 4})
# or