| Summary: | Using Advance 1 Screen sometimes jumps to wrong position | ||
|---|---|---|---|
| Product: | [Applications] kst | Reporter: | Andrew Walker <arwalker> |
| Component: | general | Assignee: | kst |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 1.x | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Proposed patch | ||
|
Description
Andrew Walker
2007-03-29 19:59:06 UTC
Created attachment 20197 [details]
Proposed patch
Looks good, but it makes me just a little worried for 1.4.0 given the late date. The current behavior has been around for a long time, and hasn't been debilitating, so I reluctantly say to delay commiting this until 1.4.0 is out the door, and then commit for 1.4.1. On Thursday 05 April 2007 6:35:54 pm Andrew Walker wrote: [bugs.kde.org quoted mail] SVN commit 653144 by arwalker:
BUG:143602 Correctly handle 'advance one screen' when in 'read to end' mode
M +5 -1 kstdoc.cpp
--- branches/work/kst/1.5/kst/src/libkstapp/kstdoc.cpp #653143:653144
@@ -889,7 +889,11 @@
int fileN = V->fileLength();
bool didChange = false;
- if (f0 + 2 * n > fileN) {
+
+ if (f0 == -1) {
+ didChange = true;
+ f0 = fileN - n;
+ } else if (f0 + 2 * n > fileN) {
didChange = f0 != fileN - n;
changed = changed || didChange;
f0 = fileN - n;
|