On Monday 09 September 2002 4:47 pm, Dr. Richard E. Hawkins
wrote:
> On Mon, Sep 09, 2002 at 03:42:04PM +0100, Angus Leeming wrote:
> > On Monday 09 September 2002 3:56 pm, Dr. Richard E. Hawkins
> >
> > wrote:
> > > WHen we had the checkboxes, either the choice was
> > > persistent or the default was postscript.
> > >
> > > With the new scrolling box, it is necessary to click each
> > > and every time the window is activated, a mouseophiliac
> > > approach.
> > >
> > > hawk, mouseophobe
> >
> > Interesting. We try not to update the browser unnecessarily.
> >
> > Could you add a line
> > #include "support/lstrings.h"
> > to src/frontends/xforms/FormSendto.C and thereafter modify
> > the update method (below). I suspect that it's something
> > trivial like whitespace that's messing things up.
>
> That didn't do it, but here's another observation.
>
> When I call up export again in the same lyx session, the
> choice is still highlighted--but either it doesn't mean it, or
> it's something about the buttons, as Apply and OK are still
> greyed out.
So that means that
1. The update is working correctly (ie your previously selected
choice is still highlighted.)
2. The buttons need a validate() call.
What happens if you modify FormSendto::update() as below? (Ie,
activate the buttons if there's a selected item).
- if (browser_keys == keys)
- return;
+ if (browser_keys == keys) {
+ if (fl_get_browser(dialog_->browser_formats))
+ bc().valid(); // so that the user can press Ok
+ return;
+ }
Angus
