Closed GoogleCodeExporter closed 8 years ago
It would actually be nice to have a button or key combination to show or hide
the
overview really quickly.
Original comment by flyhighp...@gmail.com
on 19 Mar 2010 at 3:53
I guess I can do this, but which other features should remain enabled? The
scrollbar is
the whole point of the add-in, the only thing left if you disable it is
double-click
highlighting.
Original comment by mihnea.balta@gmail.com
on 30 Mar 2010 at 12:10
That's the point. Just like in Notepad++.
Taking other Notepad++ interesting features, could be interesting to highlight
words
with some specific style which remains marked after moving the cursor.
Thanks
Original comment by robertob...@gmail.com
on 30 Mar 2010 at 12:32
There are some other VS add-ins which don't play nicely with metalscroll ( such
as
http://www.devart.com/codecompare/ ) due to the change in scrollbar width. It
would
be nice to be able to quickly toggle the scrollbar as a workaround. Currently,
I'm
forced to choose between metalscroll and the others, since enabling/disabling
add-ins
and restarting VS would be too disruptive.
Original comment by ale...@gmail.com
on 12 May 2010 at 2:47
mihnea.balta: Some colleagues of mine do find the double-click highlighting
more appealing than the scroll bar. They actually asked me how to disable
rockscroll's overview (due to limited monitor width), which is what led me
here. Quick toggling is a good idea too: I'm also a fan of Google Chrome's
bookmark tool-bar toggling design. :)
Original comment by carop...@gmail.com
on 1 Jul 2010 at 8:52
I second this: for instance, my work requires the use of ReSharper, which has
an annoying toolbar that won't go away. Fortunately, they expose methods that
you can use via Macro to toggle ReSharper on and off at will without having to
close the current page.
If MetalScroll exposed similar methods, macros could be written which both
toggle Resharper off and toggle MetalScroll on (and vice versa), allowing for
those of us who prefer MetalScroll to use it the majority of the time and then
use Resharper's features only as needed (without the annoyance of manually
turning off/closing open files and reopening them). It would be an excellent
workaround to the fact that Resharper and Metalscroll's toolbars don't play
nicely together.
Original comment by alex.lor...@gmail.com
on 24 Aug 2010 at 1:10
For reference, if it helps anyone... this is the macro I currently use as a
workaround. The problem is that you have to close any files and re-open them
in order to see MetalScroll upon activating it.
Imports System
Imports EnvDTE
Imports EnvDTE80
Imports EnvDTE90
Imports System.Diagnostics
Public Module MetalScrollMacros
Sub EnableMetalScroll()
Dim metalScrollAddin As AddIn = GetMetalScrollAddin()
On Error Resume Next
DTE.ExecuteCommand("ReSharper_Suspend")
If Not (metalScrollAddin Is Nothing) Then
metalScrollAddin.Connected = True
End If
End Sub
Sub DisableMetalScroll()
Dim metalScrollAddin As AddIn = GetMetalScrollAddin()
If Not (metalScrollAddin Is Nothing) Then
metalScrollAddin.Connected = False
End If
On Error Resume Next
DTE.ExecuteCommand("ReSharper_Resume")
End Sub
Private Function GetMetalScrollAddin() As AddIn
Dim metalScrollAddin As AddIn = Nothing
For Each addinCurrent As AddIn In DTE.AddIns
If (addinCurrent.Name = "MetalScroll") Then
metalScrollAddin = addinCurrent
Exit For
End If
Next
Return metalScrollAddin
End Function
End Module
Bind EnableMetalScroll() and DisableMetalScroll() to keys as desired. It's not
great, but it's a start. The ideal situation would be for MetalScroll itself
to expose methods that allowed for its scrollbar rendering to be disabled and
enabled, so that you wouldn't have to close and reopen files (among other
things). Hopefully this workaround helps for now though.
Original comment by alex.lor...@gmail.com
on 24 Aug 2010 at 2:44
I've added the command MetalScroll.Connect.Toggle in build 1.0.9.
Original comment by mihnea.balta@gmail.com
on 14 Sep 2010 at 4:38
Ah, awesome! You rock!
Original comment by alex.lor...@gmail.com
on 19 Sep 2010 at 10:56
Original issue reported on code.google.com by
robertob...@gmail.com
on 10 Mar 2010 at 11:42