diff options
| author | corvid <corvid@lavabit.com> | 2011-01-12 03:12:02 +0000 |
|---|---|---|
| committer | corvid <corvid@lavabit.com> | 2011-01-12 03:12:02 +0000 |
| commit | 5e8985e6e0eeffa0cc84c71f8895594c374cf326 (patch) | |
| tree | 54dfa896cf3df993b30b61ebe0fd4e17453516aa | |
| parent | b77e43108fc62c1d0358f4ab6f627a8fa81c4245 (diff) | |
fltkui comment
| -rw-r--r-- | dw/fltkui.cc | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/dw/fltkui.cc b/dw/fltkui.cc index 0a4df83c..4b93b92d 100644 --- a/dw/fltkui.cc +++ b/dw/fltkui.cc @@ -829,6 +829,15 @@ Fl_Button *FltkRadioButtonResource::createNewButton (core::Allocation return button; } +FLTK 1.3's Browser doesn't seem to permit a hierarchy, so I think we'll +use Choice and Tree. There is no Item or ItemGroup, but I see they both +have an add("menu/sub/sub/leaf") interface (not based on a common +ancestor, though), so maybe SelectionResource's job will be to keep +track of our menu-adding string or something. This will be experimental +enough that I don't want to write the code until dw's in good enough shape +to test whether I'm going about it sensibly. + + // ---------------------------------------------------------------------- template <class I> FltkSelectionResource<I>::Item::Item (Type type, |