OK, I found a workaround for my GUI ( which should take place in
app-devel-list ), keeping SELECTION_SINGLE.
As regards the GtkWidgets code, it seems to be a fragile building.
Anything you touch in there leads to side-effects.
( You talk of "evil code" in gtkcombobox.c, and you are right )
-----------------------------------
If you are interested, short resume:
-----------------------------------
In fact, with SELECTION_NONE, it is working...but you cant see the
GtkCellRendererCombo's popup because the treeview immediately do
"stop_editing" in its "button-press-event" handling.
So I connected my code to that signal, and returned TRUE for stopping
event propagation when the good cell was clicked on screen.
It worked half : short and long (no release) mouse button clicks caused
the popup to appear, but normal clicks still lead to popup vanishing.
-----------------------------------
So letting this down, thread closed -
Thank you for your answer.
On 02/08/2012 10:24 PM, Kristian Rietveld wrote:
On Feb 8, 2012, at 10:05 PM, earlgrey wrote:
----------------------------------------------------------------------
...
if ((anchor&& !gtk_tree_path_compare (anchor, path))
|| !_gtk_tree_view_column_has_editable_cell (column))
...
----------------------------------------------------------------------
What does the "!" before "
_gtk_tree_view_column_has_editable_cell
(column)" stand for ?
It was introduced to:
* gtk/gtktreeview.c (gtk_tree_view_button_press): send cell event
on first click when cell isn't editable
to fix #77862.
However, when this fix was introduced, cursor was used in the if-statement
instead of anchor, which might be why things changed?
regards,
-kris.
_______________________________________________
gtk-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
