#59803: three possibilities to fix it



Hi all,

While trying to fix #59803 (GtkEditable needs signals) I found out that
the GtkEditableClass currently has an insert_text virtual function, and
the insert_text signal (and some others) from GtkEntryClass has to be
moved to GtkEditableClass in order to fix this bug. Problem is that the
GtkEntry implementation is not just a wrapper around insert_text.

I discussed this problem with Owen on IRC, Owen came up with the following
three possibilities:

1) Add do_insert_text() do_delete_text() virtual functions to go along
with the insert_text, delete_text default handlers
2) Move what is currently in gtk_entry_insert_text() to
gtk_editable_insert_text
3) Drop this idea

[Dis]advantages:
1) Is most flexible and easiest to implement
2) Would ensure consistent behavior between different GtkEditable
implementations and is a little less clumsy than having two entries in the
GtkEditableClass structure, but sort of moves away from the idea that an
interface just an interface, and not implementation
3) Probably has no advantages over 1)

Any other ideas/thoughts?

regards,


	Kris





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]