Highlight match doesn't work with long scrolls.

We use the 9.1 version. ( sql 2008 , ssms 2014)

When I want to see a match for begin-end (in cases where it all fit the screen) - I do see it in the right way :

https://i.stack.imgur.com/8chyl.png

However - when I click on a "begin" word ( where the END is far down the scroll) :

https://i.stack.imgur.com/XNbEO.png ,

When I go to see the "END" match - I don't see any highlight :

https://i.stack.imgur.com/qytGZ.png

It seems that it only works for 100% visible in screen scopes.

Any solution ?

Hi,

The color of highlighting indicates that's not SQL Assistant's highlighting. SQL Assistant's highlighting is yellow and it is also sticky. when you scroll without changing cursor position, it doesn't change. It also uses mouse-over hints for BEGIN-END navigation. Here is my screenshot.

I suspect that you use some other addon or something in SSMS 2014 that is interfering with SQL Assistant, please try disabling that feature and allowing SQL Assistant handle bracket and BEGIN-END matching and highlighting.

--

No - it's just becuase I set the color

https://i.stack.imgur.com/iWfhS.png

Other extensions ( ssmsboost & ssmsTools) don't have that feature at atll.

Other collegues which only have SQL ASSISTNAT ( without my 2 extensions) also say that scroll is not keeping the selected word.

BTW - I do see the popup but that's not what im after

I want to click on a "begin" ------ scroll long-------- and see the "end" as selected

How do you scroll the editor? Do you use mouse and the vertical scroll bar? Mouse wheel, keyboard?

Please try the same in SQL Assistant SQL Editor. Is the selection sticky in the SQL Editor?

	SysOp wrote:
	How do you scroll the editor? Do you use mouse and the vertical scroll bar? Mouse wheel, keyboard? Please try the same in SQL Assistant SQL Editor. Is the selection sticky in the SQL Editor?

with SQL editor it's fine.

Both with mouse scroll and scroll via scrollbar - the mark is gone

if you want teamviewer please reply to [namir dot 78 at google]

What's the full version number for your version of SSMS?

	SysOp wrote:
	What's the full version number for your version of SSMS?

Microsoft SQL Server Management Studio 12.0.4232.0
Microsoft Analysis Services Client Tools 12.0.4232.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.9600.18665
Microsoft .NET Framework 4.0.30319.42000
Operating System 6.1.7601

I can confirm this in

	Quote:
	Microsoft SQL Server Management Studio 13.0.16106.4 Microsoft Analysis Services Client Tools 13.0.1700.441 Microsoft Data Access Components (MDAC) 10.0.14393.0 Microsoft MSXML 3.0 6.0 Microsoft Internet Explorer 9.11.14393.0 Microsoft .NET Framework 4.0.30319.42000 Operating System 6.3.14393

I think there's a glitch in how SSMS (or SA) handles coloring the text in the editor of SSMS. It seems that whenever one of the matching pairs (BEGIN/END) is not visible, it won't be highlighted, and that regardless of being off screen because of the long code or being covered by something.

See example below in a video (watch it here), where I have a relatively short code that has both BEGIN and END on the same screen, visible at first and then obscured by the results pane of SSMS by dragging it over the keyword END. Scrolling back and forth not only shows that END is not highlighted but also removes it from BEGIN when it scrolls out. It leaves BEGIN highlighted when I drag the result pane.

Thank you for confirming that. I was able to reproduce it too in SSMS 2014 and 2016 versions. It works fine in previous versions. The add-ons are different for them, and the internal interfaces are different too based on different Visual Studio shell versions and APIs. I don't believe it can be fixed by changing configuration here or there. Most likely fixing that requires changes in the add-on's code.

I've created a ticket for that issue.

This issue has been confirmed by the support team. It's compatibility issue with the latest SSMS 2014 and 2016 versions. A fix for that will be provided in SQL Assistant version 9.2 Current ETA is 2 weeks from now.

	SysOp wrote:
	This issue has been confirmed by the support team. It's compatibility issue with the latest SSMS 2014 and 2016 versions. A fix for that will be provided in SQL Assistant version 9.2 Current ETA is 2 weeks from now.

Thank you.