diff options
| author | Michele Calgaro <[email protected]> | 2024-03-09 18:58:02 +0900 |
|---|---|---|
| committer | Michele Calgaro <[email protected]> | 2024-03-17 21:16:45 +0900 |
| commit | 7a7827396f90ad06945cd5a367f93d8ffd380e0f (patch) | |
| tree | c812fa6c9a336fac31583724535fbcf8fd0e5ae0 /lib/kofficecore | |
| parent | ea7a0b4d73337e0e30678300466e668179241348 (diff) | |
| download | koffice-7a7827396f90ad06945cd5a367f93d8ffd380e0f.tar.gz koffice-7a7827396f90ad06945cd5a367f93d8ffd380e0f.zip | |
Replace Qt with TQt
Signed-off-by: Michele Calgaro <[email protected]>
Diffstat (limited to 'lib/kofficecore')
| -rw-r--r-- | lib/kofficecore/KoSpeaker.cpp | 2 | ||||
| -rw-r--r-- | lib/kofficecore/THOUGHTS | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/lib/kofficecore/KoSpeaker.cpp b/lib/kofficecore/KoSpeaker.cpp index 2d1a62e2..c708dd56 100644 --- a/lib/kofficecore/KoSpeaker.cpp +++ b/lib/kofficecore/KoSpeaker.cpp @@ -289,7 +289,7 @@ bool KoSpeaker::maybeSayWidget(TQWidget* w, const TQPoint& pos /*=TQPoint()*/) else if (w->inherits("TQListBox")) { TQListBox* lb = dynamic_cast<TQListBox *>(w); - // qt docs say coordinates are in "on-screen" coordinates. What does that mean? + // tqt docs say coordinates are in "on-screen" coordinates. What does that mean? TQListBoxItem* item = 0; if (pos == TQPoint()) item = lb->item(lb->currentItem()); 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 |