summaryrefslogtreecommitdiffstats
path: root/lib/kofficecore/THOUGHTS
diff options
context:
space:
mode:
authorMichele Calgaro <[email protected]>2024-03-09 18:58:02 +0900
committerMichele Calgaro <[email protected]>2024-03-22 21:28:42 +0900
commit3723148aa321530969ae4dd7472c461b94b5405e (patch)
treee5d11a855ae5ab9b409ce5f478b3a78d310f39f5 /lib/kofficecore/THOUGHTS
parente220a1b2b9fa4c97bbcaabf51cd259e62edd3ab3 (diff)
downloadkoffice-3723148aa321530969ae4dd7472c461b94b5405e.tar.gz
koffice-3723148aa321530969ae4dd7472c461b94b5405e.zip
Replace Qt with TQt
Signed-off-by: Michele Calgaro <[email protected]> (cherry picked from commit 7a7827396f90ad06945cd5a367f93d8ffd380e0f)
Diffstat (limited to 'lib/kofficecore/THOUGHTS')
-rw-r--r--lib/kofficecore/THOUGHTS4
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/kofficecore/THOUGHTS b/lib/kofficecore/THOUGHTS
index 4a9d3579..fbfd33c2 100644
--- a/lib/kofficecore/THOUGHTS
+++ b/lib/kofficecore/THOUGHTS
@@ -11,7 +11,7 @@ of "spare precision". Another related issue is getting KOffice applications
support 1:1 sizes on the screen (i.e. that an A4 paper is A4 also on the
screen). Here the problem is that in X we can have a wide range of
resolutions (from 75 or so up to 120 dpi). We also can have different
-resolutions in X and Y direction, but as Qt only honors one of them (the
+resolutions in X and Y direction, but as TQt only honors one of them (the
Y resolution) I think it's safe to ignore the X resolution (see
QPaintDevice::x11AppDpiY()).
In lib/kofficeui we have some classes replacing QPoint/QRect (they use double
@@ -115,7 +115,7 @@ of the cases, but maybe we can make that a bit more consistent at least
among "object-based" applications like KPresenter, Kivio, and KIllustrator.
4) Printing:
-Here the problem is that even Qt has enough problems with printing :(
+Here the problem is that even TQt has enough problems with printing :(
We definitely need some magic here, because right now we don't take
any advantage of the better resolution of the printer. This will be a hard
job (and an ugly hack) even if we have accurate coordinates and so