Re: Clone hook - segfault is bad, doc'd or not

I personally vote fatal E_ERROR saying it never will, stop people dead in their tracks. Whole concept seems dumb to me when I think about graphical user interface objects. If I wanted duplicates of a GtkButton I would make build the class to how I want them to be. Not build one, mod, and clone. Does not even seem economical. But that is just me. -- Bob Majdak Jr KateOS Rofflecopter Pilot http://www.kateos.org Andrei Zmievski wrote: > Elizabeth M Smith wrote: >> Hello, >> >> I was digging through the bugs and noticed the "segfault on clone" issue >> was still there. I've been thinking that we should just hook the clone >> object handler and throw an exception/ fatal error - that way people >> know that you can't clone gtk objects and we don't let the engine go >> boom. >> >> Any opinions on the subject? (it'd fix the bug too ;) > > We haven't done this yet? I could swear I did this.. apparently not. > Should just just do an E_WARNING saying that cloning is not working? > > -Andrei >