After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 411572 - When selecting, the number of bytes displayed in the status bar is off by 1 (patch included)
When selecting, the number of bytes displayed in the status bar is off by 1 (...
Status: RESOLVED DUPLICATE of bug 564372
Product: ghex
Classification: Applications
Component: general
2.8.x
Other All
: Normal normal
: ---
Assigned To: Jaka Mocnik
Jaka Mocnik
Depends on:
Blocks:
 
 
Reported: 2007-02-24 14:17 UTC by Emil Kohn
Modified: 2009-02-09 14:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This patch attempts to fix BUG 411572 (1.46 KB, patch)
2007-02-24 14:20 UTC, Emil Kohn
none Details | Review

Description Emil Kohn 2007-02-24 14:17:28 UTC
Please describe the problem:
When selecting a portion of the file, the number of bytes selected which appears in the status bar is one less than the actually selected number of bytes.



Steps to reproduce:
1. Open a file (larger than two bytes)
2. Select the first two bytes of the file
3. Look at the status bar. 

Actual results:
The status bar says: "Offset 1: 1 bytes from 0 to 1 selected". This is incorrect IMO, because we selected 2 bytes.


Expected results:
I expect the status bar to say: It will say: "Offset 1: 2 bytes from 0 to 1 selected.


Does this happen every time?
Yes

Other information:
I will send you a patch to fix this problem.
Comment 1 Emil Kohn 2007-02-24 14:20:37 UTC
Created attachment 83237 [details] [review]
This patch attempts to fix BUG 411572

I am not 100% if I spotted all the places where the off by one errors occur.
Comment 2 Rodney Dawes 2007-08-12 17:53:56 UTC
Hrmm. It appears that the issue is that the status text doesn't get updated at the appropriate time. I'm not sure if the off-by-one issue is the real issue, but there is an issue with the status text.
Comment 3 Rodney Dawes 2009-02-09 14:59:21 UTC

*** This bug has been marked as a duplicate of 564372 ***