Yes, they are identical (checked with Beyond Compare).
Maybe itâs the âuâ in front of the â2165â version number, that confuses your version check?
Regards,
Highend
Yes, they are identical (checked with Beyond Compare).
Maybe itâs the âuâ in front of the â2165â version number, that confuses your version check?
Regards,
Highend
Ok I see the error downloading your version.
sublime.version() returns a string instead of an int, and the check for version fails.
Fixed. Thank you
Thatâs, IIRC this version checking was working on previous versions, tested with SideBarEnhancements.
Confirmed, itâs fixed. Thank you!
Is it normal that it reloads itâs settings file (./Data/Packages/User/BufferScroll.sublime-settings) on each tab change / clicking on a file in the sidebar (just for the preview, not via doubleclick to load one)?
Regards,
Highend
Yes, because the application is not sending or do not want send some âeventsâ such:
1 - Closing the application
2 - Closing a project
3 - Opening a project
Sorry for the message I have no control over that.
Regards,
A little bit, yeah but anyway, I have to live with that. Thanks again for fixing this little âbugâ so fast and for your kind responses!
Regards,
Highend
The plugin doesnât work correctly in the following scenarios.
Scenario 1:
Scenario 2:
Scenario 1:
Works as expected. If there some way to âknowâ the file is opened via âbuild screenâ Iâm happy to add the exception.
Scenario 2:
Will take a look, thanks for reporting.
Regards
Hereâs what I implemented for myself: github.com/xeno-by/dotsublime/b ⌠rScroll.py. Itâs freaking ugly, thatâs why I didnât make a pull request, but it works for me, and it solves both problems.
Actually, using on_activate doesnât play well with overlays. When I press Ctrl+G, type the line number and press Enter, Sublime fires on_activate which cancels the effect of Ctrl+G. Okay, this thing needs more workarounds.
Hereâs yet another dirty hack: github.com/xeno-by/dotsublime/c ⌠6ec#diff-0.
Now I utilize the fact that overlays never show up in window.views(), despite the fact that opening an overlay fires on_activated with an overlay view as an argument (so, overlays do have underlying views). This fact can be used to filter out and ignore on_activated of a real view that happens after quitting an overlay.
Hi
I changed ârestore scrollâ to only restore the position if the current position is (0.0, 0.0)
Iâm not sure if that solves the other problems you are seeing, I donât use build system. the problem of âexternal file changesâ has been fixed.
If you can provide a step by step guide I can try
Regards,
Hi there. I find this plugin very useful.
Unfortunately I have a problem with it. When searching for something and clicking on the editable area youâre scrolled to the top.
Steps to recreate the situation:
I also figured the thing causing this. It seems that the on_activated method is called when changing focus from search to the editor.
So by simply commenting out this method I solved it.
# def on_activated(self, view):
# if view.file_name() != None and view.file_name() != '' and not view.settings().get('is_widget'):
# # restore on preview tabs should be fast as posible
# self.restore(view)
# # overwrite restoration of scroll made by the application
# sublime.set_timeout(lambda: self.restore_scroll(view), 200)
Hereâs what I did to fix this very problem: github.com/xeno-by/dotsublime/b ⌠rScroll.py. Iâm still not very happy with my changes to titoâs original code, but now it rarely does stupid stuff, so I decided to share.
[quote]When searching for something and clicking on the editable area youâre scrolled to the top.
[/quote]
Hi sorry, I noticed the problem in minutes but forget to upload the fixed version
Since recent updates (i canât give exact date) iâm continuously face with this bug:
It mostly happens when i open a file that i havenât used for a while.