java-gnome-developer

[Java-gnome-developer] Is java-gnome thread ready?

[Tiago C. <cog...@li...>]

Lots of gui apps are threaded (at least with the threading made so easy in java)
and since i am developing a multithreaded program with gtk calls that directly
affect the main loop why isn't there a way to lock the main loop so i don't get
this kind of errors?
Xlib: unexpected async reply (sequence 0xbcb)!

I tried to implement a lock mechanism in java side and mainIteration() but after
browsing gtk+ faq i found this link:
http://www.gtk.org/faq/#AEN453
So gtk is thread safe and there are mechanisms to do what i suppose is giving me
such an head ache, do you have plans implementing this?
Anyway, I will try to implement it now so i stop getting so frustrated with
java-gnome programming, where errors appear and i don't even have a clue where
they are coming from.

As soon as i finish i'll send it over to the developers mailing list and post it
as a patch in sourceforge

Still waiting for any feedback,

Tiago Cogumbreiro

Re: [Java-gnome-developer] Is java-gnome thread ready?

[Mark H. <mh...@de...>]

On Fri, Aug 08, 2003 at 06:45:56PM +0000, Tiago Cogumbreiro wrote:
> Still waiting for any feedback,

Hi,
  I can't speak for the other developers, but I've been too busy with
real life lately. I'll try to find time to answer your questions in full
later today. 

As for the threading, take a look at org.gnu.glib.CustomEvents. This
should do what you need. glib.Timer may also be useful depending on your
needs. 

Hope that helps a little. 

-- 
  .''`. Mark Howard
 : :' :
 `. `'  http://www.tildemh.com 
   `-   mh...@de... | mh...@ti... | mh...@ca... 

Re: [Java-gnome-developer] Is java-gnome thread ready?

[Tiago C. <cog...@li...>]

> Hi,
>   I can't speak for the other developers, but I've been too busy with
> real life lately. I'll try to find time to answer your questions in
> full
> later today. 
A reply in what concerns to the patches i've sent would be greatly appreciated

> 
> As for the threading, take a look at org.gnu.glib.CustomEvents. This
> should do what you need. glib.Timer may also be useful depending on
> your
> needs. 
Great! No more xlib async errors :) Thank you so much, i was getting so
frustrated with all this, now i can go on developing my java-gnome powered app ;)

Re: [Java-gnome-developer] Is java-gnome thread ready?

[Jeffrey M. <ku...@zo...>]

> A reply in what concerns to the patches i've sent would be greatly appreciated

I was on vacation last week and didn't have access to email.  Just
getting back to work this week and trying to catch up.  I will take
a look at your patches this evening.

-Jeff

Re: [Java-gnome-developer] Is java-gnome thread ready?

[Tiago C. <cog...@li...>]

> > A reply in what concerns to the patches i've sent would be greatly
> appreciated
> 
> I was on vacation last week and didn't have access to email.  Just
> getting back to work this week and trying to catch up.  I will take
> a look at your patches this evening.
> 
> -Jeff
> 

Great! :) 
One more thing in the patch i didn't remove _all_ the debug messages that were
present in CellRenderTextEvent class.

Do you know why when you retrieve a checkbox state it outputs this message?
(Mirror CD:1915): GLib-GObject-WARNING **: gvalue.c:86: cannot initialize GValue
with type `gchararray', the value has already been initialized as `gchararray'

This also appears when you try to retrieve a CellRendererToggle state

Tiago Cogumbreiro

Re: [Java-gnome-developer] Is java-gnome thread ready?

[Mark H. <mh...@de...>]

On Tue, Aug 12, 2003 at 11:43:28PM +0000, Tiago Cogumbreiro wrote:
> Do you know why when you retrieve a checkbox state it outputs this message?
> (Mirror CD:1915): GLib-GObject-WARNING **: gvalue.c:86: cannot initialize GValue
> with type `gchararray', the value has already been initialized as `gchararray'
> 
> This also appears when you try to retrieve a CellRendererToggle state

Also in a lot of other places - I get it a lot when adding rows to a
liststore. I guess it must be something to do with Value or Type. I've
never been able to track it down though. 

-- 
  .''`. Mark Howard
 : :' :
 `. `'  http://www.tildemh.com 
   `-   mh...@de... | mh...@ti... | mh...@ca...