Posted 15 years ago by Actipro Software Support - Cleveland, OH, USA
A new SyntaxEditor (for WinForms) maintenance release is now available. Updates include:
- Added code to clear the outlining nodes when the Document.LexicalParsingEnabled property is set to false.
- Added an overload to the SpanIndicatorLayerCollection.AddDisappearingSpanIndicator method that accepts an existing DisappearingSpanIndicator instance.
- Added code to the ISemanticParseDataTarget.NotifySemanticParseComplete callback in the Document class so that it will do no processing if the Document has been disposed.
- Added code for where when two SyntaxEditors are editing the same Document, changes made in one editor will try not to modify the selection of the other.
- Tweaked the OutliningNode.CollapseDescendants code and how it loops through child nodes.
- Tweaked how the drawing code raises the SyntaxEditor.UserMarginPaint event.
- Unsealed the DynamicOutliningSyntaxLanguage.PerformAutomaticOutlining method.
- Fixed a bug where the line number margin wouldn't auto-expand for large line numbers in print views.
- Fixed a bug where end scopes with multiple patterns wouldn't serialize the patterns out to XML.
- Fixed a bug where using two SyntaxEditors to edit a Document in a certain rare scenario could throw and exception.
- Fixed a bug where child language back colors weren't being loaded property from merged dynamic XML definition files.
- Tweaked the parameter list display code so that it will display if there is whitespace between the member name and the open parenthesis.
- Changed quick info so that it will not display when hovered over the name of a method in the method's declaration.
- Fixed a bug where VB event declarations with an Implements specification were being marked as a syntax error.
- Fixed a bug where assemblies that had generic interfaces with type constraints of themselves could cause a stack overload exception when loading their reflection information.
- Removed code signing by default on assemblies due to issues with how Microsoft's code causes assembly loading delays on newer operating systems like Vista in a certain scenario. Code signed assemblies are available in CodeSigned child folders within the Program Files folders for the assemblies.
- Updated the Shared/WinUICore library.
Actipro Software Support