> Exceed - that's the X server thing?

Yes.

> So... you are running your app on some X11 (unix?) machine and
> displaying it on a Windows box?

Yes.

> What OS / window manager / etc is running?

The Windows box is running XP.  The FLTK app is brought up from an xterm which 
is using the Exceed (9.0.0.32) universe.  The Unix OS is 2.6.10-1.yhpc.1smp (on 
PPC) or HP-UX 11.11 (on HP).  Does the same thing from either.

I wondered if this, from Fl_Menu.cxx, was relevant:

  case FL_RELEASE:
    // Mouse must either be held down/dragged some, or this must be
    // the second click (not the one that popped up the menu):
    if (!Fl::event_is_click() || pp.state == PUSH_STATE ||
        pp.menubar && pp.current_item && !pp.current_item->submenu() // button
        ) {
#if 0 // makes the check/radio items leave the menu up
      const Fl_Menu_Item* m = pp.current_item;
      if (m && button && (m->flags & (FL_MENU_TOGGLE|FL_MENU_RADIO))) {
        ((Fl_Menu_*)button)->picked(m);
        pp.p[pp.menu_number]->redraw();
      } else
#endif
      // do nothing if they try to pick inactive items
      if (!pp.current_item || pp.current_item->activevisible())
        pp.state = DONE_STATE;
    }

Perhaps it's FLTK version-specific?  We're at 1.1.9 here.

Thanks,
KCB

> > If I have a set of Fl_Menu_Item's which contain, among other
> > things, selections which have submenus, is there a way to prevent
> > clicking on the higher-level item from undisplaying the whole
> > menu?  I guess I'm looking for the Windoze-ish behavior where when
> > you click on a menu item which has a submenu, the submenu stays up
> > so you can then click on the desired selection from it.  For
> > example, if my menu item hierarchy looks like:
> >
> > File
> >   Open
> >     Page 1
> >     Page 2
> >     Page 3
> >     ....
> >
> > and they click on File and then click on Open, I want the "Page n"
> > list to stay up until they click on one of those.  Possible without
> > great klugey machinations?
>
> I'm not sure this is actually a fltk thing - I suspect this might be
> a window manager thing.
>
> Certainly, using Xnest to run fltk apps from one machine viewed on
> another and it behaved OK...
> So, I'm not sure quite what is going on your setup.





_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to