Home Download Buy Blog Forum Support

Minimap scroll behavior has some issues.

Re: Minimap scroll behavior has some issues.

Postby Hansiek on Mon Mar 05, 2012 9:20 am

adzenith wrote:I agree—I avoid clicking on the minimap because it doesn't work how I expect it to.

Yes, I agree.. observed the same thing.
Posts: 3
Joined: Mon Mar 05, 2012 9:18 am

Re: Minimap scroll behavior has some issues.

Postby wuub on Wed Mar 07, 2012 4:26 pm

I understand why minimap works the way it does right now and changing it to work differently removes some counter-intuitive behavior but introduces a whole new set of artifacts.

What I noticed is that minimap behaves as expected when it fits within window's height. So maybe adding an option "fit_minimap_to_window_height" (i.e. turning this http://i.imgur.com/4Em2j.png into this http://i.imgur.com/mpasv.png) is a solution that everyone was looking for?

I'm pretty sure I would trade a nice looking minimap with correct aspect-ratio for "click-to-show" behavior.
SublimeREPL via Package Control Twitter: @wuub
Posts: 161
Joined: Wed Aug 10, 2011 8:16 am
Location: Poland

Re: Minimap scroll behavior has some issues.

Postby man4mac on Fri Mar 23, 2012 6:18 pm

The current functionality of the mini map is useless honestly. Its only functional in files that really don't scroll hardly at all, and at that point I dont really use the scrollbar anyway. The functionality suggested earlier in this post (with a link to another site: http://sublimetext.userecho.com/topic/7 ... ouse-over/) is brilliant. Mousing over the minimap would show the relative location of the cursor to the viewport to the map, so clicking on any area of the minimap would bring you directly there, also it would speed up looking through very long files since the mouseover would accelerate the minimap proportional to the viewport (to get to the bottom of the minimap for the file you would only need to move the cursor to the bottom of the screen)

Please add this! if not can we at least have a way to completely disable actions from clicking on the minimap?
Posts: 1
Joined: Fri Mar 23, 2012 6:13 pm

Re: Minimap scroll behavior has some issues.

Postby misterW on Fri Jul 27, 2012 6:03 am

I just want to echo the concerns.. coming from a first time sublime user and first time minimap user, this is very un-intuitive. At least have a setting where this is configurable.
Posts: 1
Joined: Fri Jul 27, 2012 3:22 am

Re: Minimap scroll behavior has some issues.

Postby phillip.koebbe on Fri Jul 27, 2012 12:41 pm

I wanted to use the minimap, and still do. But since I can't click to go to a specific place, I just hide it and get on with life. I agree, it seems unintuitive on large files, and that seems to be the use-case where it is move valuable.
-- Phillip

Code: Select all
while self.living? do
    mistake = Mistake.new
    self.learn_from!(mistake) unless mistake.fatal?
Posts: 208
Joined: Tue Dec 20, 2011 4:58 pm

Re: Minimap scroll behavior has some issues.

Postby unphased on Mon Apr 29, 2013 10:00 pm

So I dug up a post where it was explained:

This means that if click-to-scroll was still implemented, I'd have to choose between one of two behaviours:
- The view is scrolled to the text in the minimap that you clicked on. This would result in the orange view port representation _not_ moving to where you click, which would likely be unexpected.
- The view port is scrolled to where you click. This would result in in the text you clicked on in the minimap _not_ being the text you now see in the main view, which would also be unexpected.

It is my opinion that the first behavior is a hell of a lot more unexpected than the second one. Who cares if the highlighted area moves less than you expected it to? We want to go to where we click, not go to some place we can't see.

I know this is really super-nitpicky, but the quality of Sublime is so high already as it is that the only things left to deal with are these nitpicky issues. And this one's beginning to bother me a whole lot.

The only use case (that I do admit I do occasionally, since I can't use it the other way) is to scroll around a document quickly across the entire document by scrubbing the minimap.

BUT I believe there is a way to reconcile this in such a way that **only if you drag** does it treat the vertical space as the full document. If you do a quick click on an area outside, it should definitely take you to where it was clicked. Repeating clicks in this fashion will let the highlight-block eventually reach that position after all. So which behavior it takes should depend on whether the click lands on the highlight or not. No Ctrl+click or right-click or any madness like that.

This will be reminiscent of scrollbar functionality which does page-up or page-down when clicking in the empty regions, except we have visual feedback and control. It's actually perfect.
Posts: 29
Joined: Thu May 17, 2012 5:16 am

Re: Minimap scroll behavior has some issues.

Postby unphased on Mon May 06, 2013 9:04 pm

So let me summarize/revise the usability idea for the minimap a bit:

Click the highlighted area: Treat as full file scrollbar (exactly same as it is now)
Click anywhere outside the highlighted area: Warp to the exact location the mouse is over. For large files, this will NOT allow access to the whole file.

The rationale is that the highlighted area is always quite large. If you want to scrub across the whole file, all you have to do is start dragging by clicking the highlighted area. Clicking on the rest of the area, though, will now do something really useful, i.e. allow for precise higher-level navigation; it's accelerated non-full scale scrubbing.

In addition to this, I think a really nice touch would also to be have different scroll wheel behavior: Scrolling while the mouse is over the minimap should scroll much faster than usual, this way you can navigate around a file and adjust the minimap's location more easily (because it now requires clicking and dragging on the highlight in order to move very far).
Posts: 29
Joined: Thu May 17, 2012 5:16 am

Re: Minimap scroll behavior has some issues.

Postby unphased on Mon Jul 22, 2013 3:21 pm

I just saw this implemented in 2.0.2 (and I haven't tested on 3 yet but I trust it will be there too 8-) ) Love it!

This is giving me the warm and fuzzies. Thanks for paying attention, and keep up the great work!

I suggest the title of this thread be edited to indicate the behavior has been improved (to the point where I can't see anything wrong with it, at least).
Posts: 29
Joined: Thu May 17, 2012 5:16 am


Return to Technical Support

Who is online

Users browsing this forum: Exabot [Bot] and 19 guests