Hi,
thank you all for input.
>
> Le 10/06/2010, Shawn Bakhtiar a écrit :
> > 2.2) There is probably a memory leak somewhere. Where the structure of
> > the application (the compiled code) puts that pointer outside the
> > reach of the overflow so when you re-wrote it, it magically worked
> > (vo
On Thu, Jun 10, 2010 at 06:39:30PM +0200, Michael T. wrote:
>
> Yes it does. I tried 10 other ways and they didn't work. This one
> works perfectly (so far).
> ...
>
> All initialization was shown in the previous examples. All my
> initializations are taken directly from the GTK+ documentation an
Hello,
Le 10/06/2010, Shawn Bakhtiar a écrit :
> 2.2) There is probably a memory leak somewhere. Where the structure of
> the application (the compiled code) puts that pointer outside the
> reach of the overflow so when you re-wrote it, it magically worked
> (voodoo appearing indeed).
I agree on
Jun 2010 18:39:30 +0200
> To: y...@physics.muni.cz
> From: mys...@seznam.cz
> Subject: Re: GTK Widget assertion problem
> CC: gtk-app-devel-list@gnome.org
>
> Hi,
> >
> > Hello, this all looks like utter voodoo.
>
> Yes it does. I tried 10 other ways and they d
Hi,
>
> Hello, this all looks like utter voodoo.
Yes it does. I tried 10 other ways and they didn't work. This one works
perfectly (so far).
> You have probably a trivial
> bug somewhere (elsewhere) in your code, maybe some
> extern/static/initialization confusion?
All initialization was sho
On Thu, Jun 10, 2010 at 01:31:33PM +0200, Michael T. wrote:
> In case anyone's interested I solved the problem with a little hack.
> I create the progress bar this way:
>
> progBar = gtk_progress_bar_new();
> gtk_box_pack_start (GTK_BOX (vboxGr), GTK_PROGRESS_BAR(progBar), FALSE,
> FALSE, 0);
>
In case anyone's interested I solved the problem with a little hack.
I create the progress bar this way:
progBar = gtk_progress_bar_new();
gtk_box_pack_start (GTK_BOX (vboxGr), GTK_PROGRESS_BAR(progBar), FALSE, FALSE,
0);
gtk_widget_show (progBar));
progressBarHack(progBar);
the function progr
