Would be nice if you could point out there places you found it to be
using the QGraphicsView wrongly. Some of the issues are due to us
having to keep supporting QWebView which can make it tricky at times,
so if you find any issue, please let us know.
Kenneth
i did. with code showing the
I will try to search for it :-) I get hundreds of bug e-mails per day :-)
Kenneth
On Tue, Mar 23, 2010 at 2:51 PM, Aaron J. Seigo ase...@kde.org wrote:
On March 23, 2010, Kenneth Christiansen wrote:
Would be nice if you could point out there places you found it to be
using the QGraphicsView
Hi there,
Cool stuff. I don't know about the Plasma naming, but we are trying to
not call anything but base classes for *Widget.
Plasma widgets are by default GraphicsItems right? So what about
Plasma::WebSlice? and then call the QWidget for KWebSlide?
Just a suggestion :-)
Kenneth
On Thu,
some times along the way :-))
If you go with KGraphics, I would prefer KGraphicsWebSlide.
Cheers!
On Thu, Nov 12, 2009 at 11:05 PM, Aaron J. Seigo ase...@kde.org wrote:
On November 12, 2009, Kenneth Christiansen wrote:
Plasma widgets are by default GraphicsItems right? So what about
Plasma
Hi there,
Strange...
We merely fixed the behavior to be as expected and documented.
setHtml was totally broken. It was adding the baseurl to the session
history if one was supplied, and not adding anything if nothing was
supplied. That has now been fixed.
So I wonder why this stopped working,
this whas added to achieve scrolling by flicking (even in an animate way, by
dragging fastly the webview and launching it)
right now is done by a private class (right now with timers, will be ported to
kinetic) that sets the scrollvalue properties to achieve that.
seems a sane approach?
So
Any change of QtCreator (/KDevelop) integration?
Looks pretty nice btw :-)
Cheers,
Kenneth
On Tue, Mar 31, 2009 at 6:21 PM, Diego Casella polentino...@gmail.com wrote:
Hello guys,
I made some changes on my PlasMate proposal, and also I added a screenshot
about the main window ( I think the
