Posted 13 years ago by Marianne
Avatar
If I have a double quote set as a trigger it will fire if the language is not a child language. For example, it will work if the language is directly set to VBScript, but it will not work if it is set to ASP, which contains the child VBScript language. In that case the trigger only fires with VBScript. This is not the case with any other triggers, it only seems to affect the double quote.

------------------------------- Marianne

Comments (3)

Posted 13 years ago by Marianne
Avatar
Anyone?

------------------------------- Marianne

Posted 13 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Hi Marianne,

Sorry about not replying... looked at it the other day and am still pondering how to solve it. The problem is how the value of the LexicalState property (used to check against the valid states for the trigger) is returned. If the token is a scope pattern (like " is in VBScript because it starts a string), the LexicalState is retrieved by looking at the lexical state of the parent token.

With an unmerged language, the parent token of a string is probably null, so the default lexical state of the language is used. However in a merged language scenario, the parent token is the > at the end of the SCRIPT tag. And its lexical state is in the HTML language. So the valid state requirement doesn't pass, meaning the trigger doesn't fire.

That's the problem, so we're still trying to think of a way to work around it.


Actipro Software Support

Posted 13 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
This is now fixed for the next maintenance release.


Actipro Software Support

The latest build of this product (v2020.1 build 0400) was released 26 days ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.