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 759762 - Cursor is beyond the screen when starting file comparison on Windows
Cursor is beyond the screen when starting file comparison on Windows
Status: RESOLVED DUPLICATE of bug 748715
Product: meld
Classification: Other
Component: filediff
3.14.x
Other Windows
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2015-12-21 23:56 UTC by Egor
Modified: 2016-01-08 20:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Two files in archive: file1.ini and file2.ini (6.34 KB, application/x-7z-compressed)
2015-12-21 23:56 UTC, Egor
Details

Description Egor 2015-12-21 23:56:56 UTC
Created attachment 317761 [details]
Two files in archive: file1.ini and file2.ini

Two files attached (file1.ini and file2.ini) differ in the only place - at line #768.
When starting file comparison, lines #267-295 (usually, but not always) are shown in the meld window.
Buttons "Go to the previous/next change" are disabled, as there is only one difference, and the cursor is already on that line.
But the line #768 under cursor is invisible - it is beyond the screen.

Moreover, clicking on the vertical scrollbar moves scrollbar's thumb to wrong location (not the location that was clicked on).

The most weird fact: the bug disappears when renaming the files from .ini to .txt.

Meld version 3.14.2.
Tested on two Windows7 machines with different screen resolution.
Linux version seems to be OK.
Comment 1 Kai Willadsen 2016-01-07 20:25:36 UTC
If I understand the problem correctly, I think this is a duplicate of bug 748715. The fix here looks to be for us to update the GTK+ libraries we're using.

The problem with the scrollbar moving to the wrong position should already be fixed in 3.15.x.
Comment 2 Egor 2016-01-08 20:37:48 UTC
Thank you!

Yes, it is the same bug.

Updating PyGI to version 3.18.2 does solve the problem (it was 3.14.0 before on my machine).
Updating Meld to 3.15 is not required to fix this bug (I'm still on 3.14.2 and it works fine).

Probably, some kind of "Your PyGI is rather old, please update" reminder should be embedded in Windows version of Meld?

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