diff options
Diffstat (limited to 'lib/kofficecore/THOUGHTS')
| -rw-r--r-- | lib/kofficecore/THOUGHTS | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/lib/kofficecore/THOUGHTS b/lib/kofficecore/THOUGHTS index f0121aa9..5d0a9338 100644 --- a/lib/kofficecore/THOUGHTS +++ b/lib/kofficecore/THOUGHTS @@ -28,9 +28,9 @@ just agree that this QRect represents screen pixels at the given zoom value(s) and the app can calculate the requested area to be painted itself. This should solve zooming and "scrolling" problems. One ugly problem also is what we will do about performance problems on -repainting a part. Some time ago we got a mail on KOffice where some guy +tqrepainting a part. Some time ago we got a mail on KOffice where some guy asked what to do about making that embedded painting faster. The reason is -that we *always* repaint the whole area, no matter what. This can easily be +that we *always* tqrepaint the whole area, no matter what. This can easily be optimized to a WNorthWestGravity like behavior, because you can't edit those embedded parts anyway, so even kchart and other non-WNG apps support that. ( we have to translate the painter, of course). @@ -44,7 +44,7 @@ whether they are the root views (not embedded), or they are *active* embedded views. There only has to be a KoView object. There is *one* zoom factor for both axes (x/y) and the whole -content (text, objects, children,...) is zoomed accordingly. +content (text, objects, tqchildren,...) is zoomed accordingly. This kind of zooming is like the zoom support you know from other applications. @@ -72,12 +72,12 @@ each axe here. (i.e. x/y zoom factors) Related to that is child-panning. Indepenent of the zoom factor the child shouldn't just show the left/top corner, but it should -"remember" the position inside the document when it's repainted +"remember" the position inside the document when it's tqrepainted as inactive child. ### If a part doesn't support zooming natively we have to fall back to WMartix -hacks (don't know how we can "ask" a part about that, but I'm sure we find +hacks (don't know how we can "ask" a part about that, but I'm sure we tqfind some BC way). 2.2) Widget embedding: |