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

List:       koffice-devel
Subject:    Re: Events, tools and pointer devices
From:       Boudewijn Rempt <boud () valdyas ! org>
Date:       2006-10-13 6:01:00
Message-ID: 200610130801.02404.boud () valdyas ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 12 October 2006 23:09, Cyrille Berger wrote:
> On Thursday 12 October 2006 22:50, Boudewijn Rempt wrote:
> > Any pointer event should then be passed onto the tool. Difficult
> > decision: should we make a generic pointer event that includes all tablet
> > information, or add a QTabletEvent handler to KoTool.h? Krita does the
> > first, making life easier for tool implementors, but QTabletEvent is so
> > rich, we may want to deliver it as-is.
>
> And allways deliver it even for a mouse event ? Or have tool be implemented
> for QMouseEvent and QTableEvent ?
>
> I had rather see a Ko"Input"Event, that map everything the QTableEvent.
> With a an enum Device, that is close to QTabletEvent::TabletDevice, but
> include a standard mouse device as well. It looks cleaner to me.

Okay, I will try to do that. There's already a KoPointerEvent, but it's a bit 
aenemic compared to the current KisEvent. I'll try and come up with a bit of 
a design for this, since it can become a bit complicated.

-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi

[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


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