Click on mipmap counter intuitive

[mark4]

When I click on the mipmap exploded view of the file I am editing the view should be focused on the area of the file that i clicked on. right now it behaves as if i had clicked into the scroll bar area and moves me (based on the height of the edit window) a percentage into the file.

[S0und]

short response:

+1

[facelessuser]

+1

If the minimap is just going to be a visual scrollbar, I think it would be better to only accept clicks on the view-able highlight, like a scroll-bar slider.

Though, I much prefer clicking taking me to the actually code I clicked.

The current implementation of the minimap drives me insane every time I click it. Even if it were a configurable option, that would be nice.

[nick1]

While I agree, this has been discussed before:

Minimap scroll behavior has some issues

When clicking on the minimap you should be taken directly to the area in your code that you clicked. Instead it then functions as a scroll bar of sorts. This is really evident in extremely long files. I see no value in the minimap if you can't click a code 'shape' and be delivered to it. Am I missing something?

Minimap should not react when refocussing window

When I click into a ST2 window to reactivate (= refocus = make it again to a foreground window) it (in OS X), it happens that I do so by clicking into the minimap which moves me to a completely different location in the file. I believe that in the case of reactivating a window, the minimap should not react to a click.

[mark4]

only thing confusing me is why the hell did i call it a “MIP” map… i must have been doing some graphics related stuff that day lol…