after looking over the GTK plug/socket documentation, it would work, but socket1(hardcoded socket) would have to be a socket, not a GTK socket
http://www.linuxhowtos.org/C_C++/socket.htm

and use it to get and pass the plugID

Kevin

On Mar 6, 2011 4:05pm, Michael Treibton <[email protected]> wrote:
hi,



[re-add Cc list to gtk mailing list back in.]



On 6 March 2011 19:52, Kevin Anthony [email protected]> wrote:

> I've never used GtkSocket, but i've used unix sockets, so here's a

> suggestion. your plug connects to socket1(the hardcoded socket)

> It gives a second socket name, (socket_itter++) and closes the

> connection, the plug program then conects to the softcoded socket it

> got from socket1.

>

> this makes the program scalable.



Hmm -- i think i see what you mean, but i can't see how that works

with GtkSocket.



Michael

_______________________________________________
gtk-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtk-list

Reply via email to