On Tuesday 01 April 2008 15:31:40 Bernhard Rosenkränzer wrote:
> On Monday 31 March 2008 21.25:50 Holger Freyther wrote:
> > On Monday 31 March 2008 16:26:38 Bernhard Rosenkränzer wrote:
> > > When using QWebView::setCursor, the cursor isn't actually used, because
> > > WebKit bits select different cursors depending on what HTML widget the
> > > cursor is over.
> > >
> > > I think a widget that does this needs something like
> > > QApplication::setOverrideCursor and QApplication::restoreOverrideCursor
> > > (except it affects the widget's range only).
> >
> > Would you always want to use the cursor you set? For images, zooming,
> > text selection, plugins loaded, scrolling...?
>
> In this particular case, yes:
>
> QWebView *a;
> a->setCursor(Qt::WaitCursor);
> a->evaluateJavaScript("Some JavaScript code that takes ages to complete");
> a->setCursor(Qt::ArrowCursor); //<--- this should actually go back to the
> default set of cursors, so a per-widget variant of QApplication::
> {set,restore}OverrideCursor really makes more sense.No, setCursor is the right API. It's a bug that it doesn't override the cursors specified in the HTML. There's a QWidget::unsetCursor() method as well, and that one should revert to the default behavior. Cheers, Lars To unsubscribe - send "unsubscribe" in the subject to [EMAIL PROTECTED]
