Re: GtkTreeView Search Popup

2005-09-29 Thread Christian Neumair
Am Donnerstag, den 29.09.2005, 12:46 -0400 schrieb Alex Levin: > Hello. I have an application which has a very specific UI built into > it. I have a GtkTreeView widget in which I would like to enable the > typeahead search functionality. My problem is that if I use the > gtk_tree_view_set_enable

GtkTreeView Search Popup

2005-09-29 Thread Alex Levin
Hello. I have an application which has a very specific UI built into it. I have a GtkTreeView widget in which I would like to enable the typeahead search functionality. My problem is that if I use the gtk_tree_view_set_enable_search function, a popup box with the letter typed is displayed. Does

Re: Memory question

2005-09-29 Thread Przemysław Sitek
Dnia 2005-09-29 13:56, Christian Neumair napisał: Am Donnerstag, den 29.09.2005, 13:39 +0200 schrieb Przemysław Sitek: Dnia 2005-09-29 21:41, Colossus napisał: Ok, the correct way is to cast g_strerror to (char *): response = ShowGtkMessageDialog (GTK_WINDOW (MainWindow),GTK_DIALOG_MODAL,G

Re: Memory question

2005-09-29 Thread Christian Neumair
Am Donnerstag, den 29.09.2005, 13:39 +0200 schrieb Przemysław Sitek: > Dnia 2005-09-29 21:41, Colossus napisał: > > Ok, > > > > the correct way is to cast g_strerror to (char *): > > > > response = ShowGtkMessageDialog (GTK_WINDOW > > (MainWindow),GTK_DIALOG_MODAL,GTK_MESSAGE_ERROR,GTK_BUTTONS_O

Re: Memory question

2005-09-29 Thread Przemysław Sitek
Dnia 2005-09-29 21:41, Colossus napisał: Ok, the correct way is to cast g_strerror to (char *): response = ShowGtkMessageDialog (GTK_WINDOW (MainWindow),GTK_DIALOG_MODAL,GTK_MESSAGE_ERROR,GTK_BUTTONS_OK,(char *) g_strerror(errno)); This way i don't get any warning. But it's still incorrec

Problems in Typing Vietnamese in Gtk application

2005-09-29 Thread Gaurav Jain
Hello! I have a small program (code at the end of this mail), in which I'm trying to achieve the following: - Type Vietnamese characters, such that the key-presses are processed by a GtkLayout, and the actual text is shown on a GtkLabel. I cannot directly use a GtkEntry or a GtkTextView, (which bo

Re: Memory question

2005-09-29 Thread Christian Neumair
Am Donnerstag, den 29.09.2005, 12:42 +0200 schrieb Christian Neumair: > 1 foo (const void *bar); and > 2 foo (void **bar); Should have a void retval. Sorry for the confusion. -- Christian Neumair <[EMAIL PROTECTED]> ___ gtk-app-devel-list mailing lis

Re: Memory question

2005-09-29 Thread Christian Neumair
Am Mittwoch, den 28.09.2005, 21:44 -0400 schrieb Allin Cottrell: > On Wed, 28 Sep 2005, David Rosal wrote: > > > Allin Cottrell wrote: > > > >> gchar *text = g_strdup_printf("banana %d", i); > >> gtk_entry_set_text(GTK_ENTRY(entry), text); > >> g_free(text); > > > > Is the above code really safe?

Re: Memory question

2005-09-29 Thread Colossus
Ok, the correct way is to cast g_strerror to (char *): response = ShowGtkMessageDialog (GTK_WINDOW (MainWindow),GTK_DIALOG_MODAL,GTK_MESSAGE_ERROR,GTK_BUTTONS_OK,(char *) g_strerror(errno)); This way i don't get any warning. Colossus wrote: Hi, I did as you suggested me but gcc 3.4.3 give

Re: Memory question

2005-09-29 Thread Colossus
Hi, I did as you suggested me but gcc 3.4.3 gives me this warning: callbacks.c:605: warning: passing arg 5 of `ShowGtkMessageDialog' discards qualifiers from pointer target type and the line 605 is: response = ShowGtkMessageDialog (GTK_WINDOW (MainWindow),GTK_DIALOG_MODAL,GTK_MESSAGE_ERROR,G

Re: Memory question

2005-09-29 Thread Christian Neumair
Am Mittwoch, den 28.09.2005, 10:58 +0200 schrieb David Rosal: > Colossus wrote: > > Am I doing the same ( memory leaking ) with g_strdup_printf ? Yes, of course. It also allocated new memory for you, but additionally merges the ith (where ith > 1) argument of the g_strdup_printf into the string as

Re: Memory question

2005-09-29 Thread Christian Neumair
Am Dienstag, den 27.09.2005, 17:53 +0200 schrieb David Rosal: > gtk_entry_set_text(GTK_ENTRY(entry), g_strdup("banana"); > > Am I leaking memory? (...) > My question is: Is that memory chunk free'd before the program exits? If I'm taken correctly, your OS is meant to free *all* memory you allocat