Re: Copying bitmaps into bitmaps

On Thu 17 Jan 2002 13:38, Havoc Pennington wrote: Edscott Wilson García [EMAIL PROTECTED] writes: After looking at a book by Barkakati, (X Window System Programming, 1991) he says that bitmaps should be copied into pixmaps by XCopyPlane(), not XCopyArea() (the latter being used

Re: Copying bitmaps into bitmaps

On Thu 17 Jan 2002 14:21, Havoc Pennington wrote: Edscott Wilson García [EMAIL PROTECTED] writes: But isn't a bitmap nothing more than a pixmap of depth 1? If gdk_pixmap_new(window,pix_w,pix_h,1); is not the correct way to create an empty bitmap with gtk, how should it be created

got it:bitmaps

, and I'm sorry for the wasted bandwidth Edscott On Thu 17 Jan 2002 14:21, you wrote: Edscott Wilson García [EMAIL PROTECTED] writes: But isn't a bitmap nothing more than a pixmap of depth 1? If gdk_pixmap_new(window,pix_w,pix_h,1); is not the correct way to create an empty bitmap with gtk

Gtk+ starting drags by error

this (these) variable (s). Any ideas on what to initialize? Any suggestions would be greatly appreciated. Thanks in advance to any pointers, Edscott Wilson Garcia ___ gtk-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-list

forking heap problem fully solved FTR.

(route,'/'); if (end==route) end[1]=0; /* root directory */ else end[0]=0; stat(route,t_stat); free(route); } } Saludos Edscott Wilson Garcia. ___ gtk-list

Re: implementing bars in the meantime on of long work

, your child can even exec some command line utility if necesary. saludos Edscott Wilson Garcia ___ gtk-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-list

Re: forking heap question

Paul Davis wrote: parent heaps totally independent, as should be. Maybe there is a way to tell gtk at the fork point whether child or parent will keep the widgets instead of leaving it up to gtk to decide? there isn't any choice. the child cannot access the widgets. end of story. i

forking heap question

memory the problem is gone. Is this possible? Should the use of heap memory be avoided at all costs when using gtk with fork()? Thanks in advance for any clue to this puzzling dilema. Edscott Wilson Garcia ___ gtk-list mailing list [EMAIL PROTECTED

Re: forking heap question

Havoc Pennington wrote: Edscott Wilson García [EMAIL PROTECTED] writes: I was getting random io X error after forking and the child was not using any GTK, nor was it using exit() in stead of _exit(). I finally tracked down the problem to the child using malloc() and free

Re: forking heap question

Paul Davis wrote: Neither do I think it's possible. Yet, it is so. Maybe a failed malloc() no its not. virtual address spaces make it so. children have no access to their parent's address space. global variables make no difference. or free() makes the child access a gtk widget it's not

Re: forking heap question

you avoid manipulating them by accident from the process which is not supposed to, as with a memory allocation error. I've already hunted down two of them in xftree, so there might be a third, and the x-io error makes the hunting much more difficult. Edscott Ralph Walden Edscott Wilson

client/server synchronization

? Is it necesary to put in xlib code? Thanks in advance to any answer or pointer or suggestion. Edscott Wilson Garcia ___ gtk-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-list

Gtk+ bringing X down?

I wrote this program called xfsamba, which basically does a lot of forking around smbclient (from the samba suite). It uses a Ctree widget to create a graphical view and also has a text window where much of the text output from smbclient is displayed. This implies, theoretically of course, that

Re: about two-way pipes or threads

On Wednesday 14 February 2001 08:56, Ronald Bultje wrote: I have another thing. I am probably doing something terribly wrong. Can you give me the names of these applications you wrote using this technique (and/or HTTP-locations) so I can look in their source. Maybe that helps... Ronald The

<    1   2