[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: Question about KoZoomHandler
From: Boudewijn Rempt <boud () valdyas ! org>
Date: 2006-09-26 20:04:46
Message-ID: 200609262204.46189.boud () valdyas ! org
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
On Tuesday 26 September 2006 22:00, Boudewijn Rempt wrote:
> or extract a KoAbstractZoomHandler from KoZoomHandler and make
> KoZoomHandler implement both KoAbstractZoomHandler and KoViewConverter, and
> create a KisZoomHandler that does the same. How would that be? I bet it
> will show up underlying undoxed assumptions in the use of KoZoomHandler in
> the rest of KOffice :-).
I could even do a conversion to and from postscript pt (72 to the inch,
right?) where that's the given input and output, for instance in
// Input: pt. Output: pixels. Resolution and zoom are applied.
int zoomItXOld( double z ) const {
return qRound( m_zoomedResolutionX * z );
}
int zoomItYOld( double z ) const {
return qRound( m_zoomedResolutionY * z );
}
double zoomItX( double z ) const {
return m_zoomedResolutionX * z;
}
double zoomItY( double z ) const {
return m_zoomedResolutionY * z ;
}
QPoint zoomPointOld( const KoPoint & p ) const {
return QPoint( zoomItXOld( p.x() ), zoomItYOld( p.y() ) );
}
QRect zoomRectOld( const KoRect & r ) const {
QRect _r;
_r.setCoords( zoomItXOld( r.left() ), zoomItYOld( r.top() ),
zoomItXOld( r.right() ), zoomItYOld( r.bottom() ) );
return _r;
}
Or does Old not mean the previous zoom level, but that these methods should be
deprecated and/or removed?
--
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic