Stefan Kost wrote:
[...]
I think a little example and some notes as part of the longs-description
would be sufficient.
I usualy don't touch the docs, but for this I'll make an exception :-p
Cheers,
-Tristan
___
gtk-app-dev
Hi Tristan,
Greg Breland wrote:
[...]
What really needs to happen(and I believe is in the works) is that the
GTK manual needs user comments or wiki goodness. This would solve
almost everything except that each function might have too much
information before too long. :)
While we're on a ra
Greg Breland wrote:
[...]
What really needs to happen(and I believe is in the works) is that the
GTK manual needs user comments or wiki goodness. This would solve
almost everything except that each function might have too much
information before too long. :)
While we're on a rant about API doc
Hi again,
Gus Koppel wrote:
While the case of returned "const gchar *"s is rather simple, the real
problem to me is that the API docs are quite less explicit when it comes
to more complex objects than just string constants.
For instance, whether and how reference counts of objects related to
t
On Sat, 2005-07-23 at 11:29, Gus Koppel wrote:
> Arx Henrique wrote:
> I wish the API docs would be added a line for _every_ get- or set-
> function, which explicitly notes whether and how reference counts of
> associated objects are changed by that function.
What really needs to happen(and I bel
Gus Koppel wrote:
>While the case of returned "const gchar *"s is rather simple, the real
>problem to me is that the API docs are quite less explicit when it comes
>to more complex objects than just string constants.
>
>For instance, whether and how reference counts of objects related to
>treeviews
On Sat, Jul 23, 2005 at 06:29:17PM +0200, Gus Koppel wrote:
>
> I wish the API docs would be added a line for _every_ get- or set-
> function, which explicitly notes whether and how reference counts of
> associated objects are changed by that function.
Take a look at the following wiki page. If
> I wish the API docs would be added a line for _every_ get- or set-
> function, which explicitly notes whether and how reference counts of
> associated objects are changed by that function.
I second that motion! Actually, I wish it would be a standard for all
GNU-style open source projects. I thi
Arx Henrique wrote:
> > > my doubt is g_free or not g_free the text?
> >
> > When in doubt, read API docs:
>
> Tks x)
> next time i'll read api
While the case of returned "const gchar *"s is rather simple, the real
problem to me is that the API docs are quite less explicit when it comes
to more
On Fri, 22 Jul 2005 16:31:39 -0300
Arx Henrique <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> i have a GtkEntry with a signal "activate" and this handle:
>
> void translate(GtkEntry *widget, gpointer *data) {
> const gchar *text;
> text = gtk_entry_get_text(widget);
> gui_app_notify
Le vendredi 22 juillet 2005 à 16:31 -0300, Arx Henrique a écrit :
> Hi all,
>
> i have a GtkEntry with a signal "activate" and this handle:
>
> void translate(GtkEntry *widget, gpointer *data) {
> const gchar *text;
> text = gtk_entry_get_text(widget);
> gui_app_notify_new(text)
Tks x)
next time i'll read api
On 7/22/05, David Necas (Yeti) <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 22, 2005 at 04:31:39PM -0300, Arx Henrique wrote:
> > i have a GtkEntry with a signal "activate" and this handle:
> >
> > void translate(GtkEntry *widget, gpointer *data) {
> > const gchar
On Fri, Jul 22, 2005 at 04:31:39PM -0300, Arx Henrique wrote:
> i have a GtkEntry with a signal "activate" and this handle:
>
> void translate(GtkEntry *widget, gpointer *data) {
> const gchar *text;
> text = gtk_entry_get_text(widget);
> gui_app_notify_new(text);
> g_free(
Hi all,
i have a GtkEntry with a signal "activate" and this handle:
void translate(GtkEntry *widget, gpointer *data) {
const gchar *text;
text = gtk_entry_get_text(widget);
gui_app_notify_new(text);
g_free(text);
gtk_editable_delete_text(GTK_EDITABLE(widget
14 matches
Mail list logo
