search

hakaishi / nobleNote

Program to make and manage notes
Other
30 stars 4 forks source link

when scrolling a note, view scrolls not from same position where it was left, but a bit above #199

Closed revast closed 6 years ago

revast commented 6 years ago

This is a bit annoying, because you scroll down to get a bit further down the note, but it starts scrolling to the same position where you just left

nebomuk commented 6 years ago

I cannot reproduce the issue on Qt 5.11, Ubuntu 18.04. Could you please add a bit more details to your description? What platform and Qt version are you using? Did you use the mouse wheel or the scroll bar for scrolling? How large is the text document you are scrolling (this influences the size and behaviour of the scroll bar)?

revast commented 6 years ago

18.04, qt 5.9, mouse wheel, scrolling down:

scroll

hakaishi commented 6 years ago

Hi revast. For me and taiko000 the issue is not very clear. Are you saying that you scroll down, but after releasing the scroll wheel it automatically scrolls back to the previous position? Does this have anything to do with the cursor position? Like, for example if you put the cursor on the bottom of the page and scroll to the top, you will end up at the bottom of the page. And verse visa if you put it on the top of the page?

There are three possible problems here: A compatibility bug of Qt and you system, a general bug of the Qt version you are using, or a setting problem on our side. In the last case, I would guess that Qt is introducing (or tying to do so) a new feature and we didn't catch up with it. We will try to check that out.

Could you please also confirm if you got this kind of issue: https://askubuntu.com/questions/715581/qtcreator-scroll-jumps-after-mouse-click?rq=1

best regards, Christian

revast commented 6 years ago

I also had this on 16.04, now using 18.04 with 1.1.0beta4

when you just used the mouse whell as you normally would to scroll down the text..it started to scroll from a bit above the current position. BUT... I have now retried with dev branch - there it is working properly.

So I think we can close this issue..