[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: popup completion
From:       Dawit Alemayehu <adawit () kde ! org>
Date:       2000-11-15 7:09:06
[Download RAW message or body]

On Tuesday 14 November 2000 15:32, Tobias Anton wrote:
> On Tuesday 14 November 2000 18:40, Dawit Alemayehu wrote:
> > On Saturday 11 November 2000 16:50, Carsten Pfeiffer wrote:
> > > On Sat, Nov 11, 2000 at 09:41:02PM +0100, Daniel Naber wrote:
> > >
> > > Hi,
> > >
> > > > can someone perhaps compare our popup completion with the one of
> > > > MSIE? I think they should act the same unless there are good
> > > > (usability) reasons to do it another way. Things to test:
> > >
> > > yes.
> > >
> > > > -Is one return enough to go to the URL or will it only copy the
> > > > selected URL to the location bar (konqi does that currently)?
> > >
> > > I think it should, it's just not done yet.
> >
> > Hmmm... this currently does not work anymore.  Something changed in
> > QComboBox to break this.  Ahhh... I see QLineEdit is being used as the
> > FocusProxy widget for QComboBox resulted in that.  I will have to fix
> > that as well....
>
> I suspect that this also caused the following strange behaviour:
> when navigating html via keyboard, the combobox only gets the focus only
> once every two "round-trips". Else, the location bar is simply skipped.
>
> Could that be?

Nope.  If a widget is made a FocusProxy, it simply means that all the events are
propagated to the proxy widget.  In the case of QComboBox, QlineEdit is the widget
that actually receives all the focus events and handles them appropriately.  The other
problem you metioned is caused by something else.  IIRC Daivd already fixed the exact
same problem a while back by chasing down the focus event propagation to see where
it was going...

Regards,
Dawit A.

[prev in list] [next in list] [prev in thread] [next in thread]