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 748715 - Doesn't scroll to first difference on start with gtk to 3.14 (pygi-aio-3.14.0_rev17-setup.exe)
Doesn't scroll to first difference on start with gtk to 3.14 (pygi-aio-3.14.0...
Status: RESOLVED OBSOLETE
Product: meld
Classification: Other
Component: filediff
3.13.x
Other Windows
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
: 759762 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-04-30 16:31 UTC by Vasily Galkin
Modified: 2016-01-08 20:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vasily Galkin 2015-04-30 16:31:08 UTC
After upgrading pygobject-win32 to 3.14-rev17 the functionality of automatically scrolling to first difference after opening file diff becomes broken.

The cursor in text is correctly positioned but scroll bar's position is random (looks depending on system load) between start of file and first difference - so both cursor and first diff are out of scroll view, which is not comfortably.

After pressing any arrow scrollbar goes to correct position.
Also navigating to another difference with alt+down works.

For me the same gtk upgrade introduces smooth scrolling for win32 (at least visually it become a lot smoother), this may be related.

So it looks like gtk starts smooth scrolling to wanted position but something prevents it from continuing and it stucks at one third.
I'm not sure is this meld, gtk or gtk packaging problem.

This problem appears in meld 3.11.2 and 3.13.1 with python 2.7.6 (32-bit) and pygi-aio-3.14.0_rev17 on windows 7 x64.
Comment 1 Vasily Galkin 2015-12-28 19:08:04 UTC
No more reproduced in meld 3.15.1 with windows 7 x64 with PyGI 3.18.2 AIO for Python 2.7 32 bit.
Comment 2 Egor 2016-01-08 20:37:48 UTC
*** Bug 759762 has been marked as a duplicate of this bug. ***