Re: CTree question

["Buzz Megg" <buzmeg hotmail com>]

Okaaaay, CTree sucks.  Rewrite it.

Snide comment aside, I have a finite amount of programming time.  This 
sounds like I'm going to spend a lot of time working around CTree that would 
be better off spent working *on* CTree.

CTree kinda sucked two? years ago when I first used it as part of gtk, and 
it still seems to suck now.  Why?  Is it lack of time?  Is it deprecated and 
everybody else uses something else (if so, what?)?
Is it a widget that should just be killed?  Does everyone else just 
specialize CList?  Why is there still no documentation on it?  Help me 
understand this and maybe I can help rectify it.

This issue came up in C++ only because STL containers want default 
constructors.  Default constructors imply being able to modify the widget 
after it is already formed.  This *can* be worked around, it's just 
annoying.

I don't know Python well enough to comment.

-a

Havoc Pennington wrote:
>CTree sucks, work around it. I don't see how the problem is unique to
>C++ though, or why C++ in particular requires this functionality more
>than C or Python.
>
>Havoc

________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com