Here's an idea:
Both TreeViews use the same model. The model has a "selected" column. The second TreeView puts the model in a TreeModelFilter, showing only the rows where selected==true.
In general, please email gtkmm-list rather than me directly.
On Wed, 2005-04-27 at 15:18 -0700, Bryce Harrington wrote:
Hi Murray,
Speaking of gtkmm, one observation/request:
We've noticed for Inkscape it would be __really__ handy to create a certain kind of dialog using the TreeView control. For things like the layer editor, extensions, preferences, XML editor, and so forth, we need hierarchical management of various XML and SVG trees.
Basically, these dialogs use a TreeView widget on the left, which allow navigating through the tree and selecting an item, and then the right side of the dialog is updated to display widgets appropriate to that selection.
This is a uber-common style of dialog for file or config management, etc. etc. Pull up Inkscape's XML Editor to get an idea of what we need.
However... The problem has been that hooking up TreeView with all the code to manage the widgets, signals, and XML tree looks really intimidating. We've not been able to find an Inkscape volunteer brave enough to dive into it.
Anyway, my thought is that this style of dialog would probably be extremely useful to other gtkmm users (in fact, I'd been planning to contribute it back to gtkmm if/when it got developed), and that perhaps the gtkmm team might be able to help in creating it? I think we could give a lot of ideas on the design and of course lots of feedback and testing as we incorporate it.
Bryce
On Tue, Apr 26, 2005 at 06:55:24PM +0200, Murray Cumming wrote:
At least with the sourceforge bug tracker you can't mark a bug as dependent on gtkmm.
-- Murray Cumming murrayc@...799... www.murrayc.com www.openismus.com