On Tue, 6 Nov 2018 at 09:55, Радомир Хаџић via gtk-app-devel-list <
gtk-app-devel-list@gnome.org> wrote:
> Hi. I get segmentation fault if I try to access a Poppler object whose
> pointer is passed through g_signal_connect. There is no such problem
> with normal pointers, though.
This:
> void
On Tue, Jul 01, 2014 at 01:39:03AM -0700, Anoop Neem wrote:
> This application is intended to convert value entered in Text entry
> field (in Celcius) to Farenheit in label. I was having hard time in
> altering the properties of two widgets (other than calling widget) in
> the same callback, hence
On Tuesday 01 July 2014 10:39:03 Anoop Neem wrote:
Hi,
try:
p->two = label = gtk_label_new(a);
p->one = textEntry = gtk_entry_new()
hope this helps,
zz
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.o
On Tue, Jul 01, 2014 at 01:39:03AM -0700, Anoop Neem wrote:
> p->one = textEntry;
> p->two = label;
Here the unititialised textEntry and label pointers are assigned to the
struct fields.
> textEntry = gtk_entry_new();
> calButton = gtk_button_new_with_label("Calculate");
I think that you want to connect to the signal "destroy-event" of
GtkWidget instead of "destroy" of GObject.
See:
http://library.gnome.org/devel/gtk/unstable/GtkObject.html#GtkObject-destroy
http://library.gnome.org/devel/gtk/unstable/GtkWidget.html#GtkWidget-destroy-event
On Fri, Feb 27, 2009 a
Thank you. My problem is solved now.
On Thu, Oct 30, 2008 at 2:20 PM, Larry Reaves <[EMAIL PROTECTED]> wrote:
> Running through gdb, we can see it crashes on this line:
>
> gtk_container_add(GTK_CONTAINER(window),menu_bar);
>
> glancing through the code, this makes perfect sense because window is
Running through gdb, we can see it crashes on this line:
gtk_container_add(GTK_CONTAINER(window),menu_bar);
glancing through the code, this makes perfect sense because window is
never initialized. The pointer window points to some random address.
Adding:
window = gtk_window_new(GTK_WINDOW_TOPLE
Hi Aparna,
Forgive me if I am wrong, but g_thread_init(NULL); gdk_threads_init();
might duplicate the call. I recall when using gnet (which initiates
the threads itself it segfaulted if I called g_thread_init. Perhaps
taking one of those out would fix your problem?
Dan
On 18-Oct-08, at 7
The problem was in the callback's arguments, thanks.
PS. Nickolai:
I cut out most of the code to make things clearer, don't worry I did
add the widgets to a table and the table to the window.
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.o
Szymon,
In addition to what Yeti has pointed out, one thing that's obviously wrong
is that you don't seem to have anything in your code that adds the text
entry
to the window, i.e.
gtk_container_add(GTK_CONTAINER(windowP), widgetP);
Also, why not use gtk_entry_get_text(...) to read the content o
On Sun, Jun 03, 2007 at 12:28:03PM +0200, Szymon Ząbkiewicz wrote:
> I'm am new to gtk+ and I try to write a simple application, I need to
> read a double from an entry, I've already written a parsing
> *char->double function
Is it really necessary to write yet another floating point
number parser
On Sat, 21 Oct 2006, Lorenzo Marcon wrote:
> Program is running without any problem under Linux, while under
> Windows, when clicking STOP I get segmentation fault.
>
> Here is the backtrace.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0040279e in enter_callback ()
> (gdb) bt ful
On Tue, 2006-04-04 at 19:38 -0400, John Vetterli wrote:
> On Tue, 4 Apr 2006, Sandeep KS wrote:
> > I have written a program using GTK which executes some shellscripts in
> > the background...After the shellscripts complete executing, a window is
> > displayed showing the completion details A
On Tue, 4 Apr 2006, Sandeep KS wrote:
I have written a program using GTK which executes some shellscripts in
the background...After the shellscripts complete executing, a window is
displayed showing the completion details At this time segmentation
fault occurs.
Is there anyway to trace the
Dnia 24-06-2005, pią o godzinie 17:25 +0100, Tim Müller napisał(a):
> On Friday 24 June 2005 16:59, Uzytkownik wrote:
> > I've problem with GHashTable:
> > (...)
> > self->private->check = g_hash_table_new(g_int_hash, g_int_equal);
> > g_hash_table_insert(self->private->check, GINT_TO_POINTER(3), "
On Friday 24 June 2005 16:59, Uzytkownik wrote:
> I've problem with GHashTable:
> (...)
> self->private->check = g_hash_table_new(g_int_hash, g_int_equal);
> g_hash_table_insert(self->private->check, GINT_TO_POINTER(3), "%%(.*)");
> (...)
g_int_hash() expects a _pointer_ to an int, not an int (see
On Fri, Jun 24, 2005 at 05:59:37PM +0200, Uzytkownik wrote:
> I've problem with GHashTable:
> (...)
> self->private->check = g_hash_table_new(g_int_hash, g_int_equal);
> g_hash_table_insert(self->private->check, GINT_TO_POINTER(3), "%%(.*)");
> (...)
>
> In unit test(I use check) it show:
> (...)
On Tuesday 21 June 2005 12:59, y g wrote:
> I had posted in the past but with no luck about segmentation faults
> that I am getting when trying to save a pixbuf into a file. With a bit
> more debugging this is the error I am getting when I try:
> gdk_pixbuf_save(pixbuf, "temp.bmp", "bmp", NULL);
>
Aaron Yang wrote:
hi, thanks for replying
after changing, segmentation fault still follows.
there's an additional error saying
warning: passing arg 2 of `g_timeout_add' from
incompatible pointer type
Use typecast: g_timeout_add (100, (GSourceFunc)real_draw, drawing_area);
compiler expects "gboolean
hi, thanks for replying
after changing, segmentation fault still follows.
there's an additional error saying
warning: passing arg 2 of `g_timeout_add' from
incompatible pointer type
in this case arg 2 is static gint real_draw (
GtkWidget * )
i figure the error occurred because it shd be
static
Aaron Yang wrote:
> void draw_button_clicked ( void )
{
1. You're passing NULL as a parameter for timeout's callback.
g_timeout_add (100, real_draw, NULL);
}
2. window parameter is NULL (see above).
static gint real_draw ( gpointer window )
{
GtkWidget *widget;
3. Variable widget is undefined,
21 matches
Mail list logo
