In Development
Last Updated: 25 Feb 2020 08:09 by ADMIN
Created by: Olivier
Comments: 1
Category: SyntaxEditor
Type: Bug Report
3

Hello,

When we resize the syntaxEditor control, the folding buttons moved. You can reproduce this isssue in your demos.

 

  1. Reduce the contents of the sample
  2. Increase the size of sample window and see the buttons are not besides the line

 

Best regards,

Unplanned
Last Updated: 17 Feb 2020 13:43 by ADMIN
Foldings are incorrect when there is a missing open or close tag.
Unplanned
Last Updated: 05 Feb 2020 15:06 by ADMIN
In some cases the string values in the XML attributes are not colored with the expected color, but default to black.
 
This was reproduced when there is only single quotation mark on visible on the line. And also if the count of the visible quotation marks on the line is an odd number (not always reproducible). 

Completed
Last Updated: 22 Jan 2020 12:34 by ADMIN
Release LIB 2020.1.127 (01/27/2020)
'Cannot find resource named 'DragVisualStyle' error occurs in in the error list when using implicit styles.
Completed
Last Updated: 25 Nov 2019 15:04 by ADMIN
Release LIB 2019.3.1202

If you have an XML attribute with a string value, but the value is not fully rendered into the viewport, its color defaults to black, instead of the expected blue color.

To work this around, you can create a custom XmlTagger and override its GetTags() method. This will allow you to properly catch the string value and return it as a tag span element with its ClassificationType set to "string".

Completed
Last Updated: 17 Oct 2019 08:29 by ADMIN
Release R3 2019 SP1
Folding tagger does not work for other languages than C#.
It should be renamed to CSharpFoldingTagger.
FoldingTagger should be base , extensible class with options to set collections of opening symbols (brackets) or words (for startinga  method / class, region) and closing symbols / words.

Unplanned
Last Updated: 27 Sep 2019 08:24 by ADMIN
For example "//====" will not be commented in C#. 
Or "!====" wont' be commented in custom language if "!" is the commenting symbol.
The issue resides in the word splitting function in WordTaggerBase class.