aboutsummaryrefslogtreecommitdiff
path: root/dw/fltkui.cc
diff options
context:
space:
mode:
Diffstat (limited to 'dw/fltkui.cc')
-rw-r--r--dw/fltkui.cc27
1 files changed, 0 insertions, 27 deletions
diff --git a/dw/fltkui.cc b/dw/fltkui.cc
index 460f312c..fe65cbd7 100644
--- a/dw/fltkui.cc
+++ b/dw/fltkui.cc
@@ -821,35 +821,8 @@ 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>::FltkSelectionResource (FltkPlatform *platform):
- FltkSpecificResource<I> (platform)
-{
- widgetStacks = new List <WidgetStack> (true);
- allItems = new List <Item> (true);
- items = new Vector <Item> (16, false);
-}
-
-template <class I> FltkSelectionResource<I>::~FltkSelectionResource ()
-{
- delete widgetStacks;
- delete allItems;
- delete items;
-}
-
template <class I> dw::core::Iterator *
FltkSelectionResource<I>::iterator (dw::core::Content::Type mask, bool atEnd)
{