When the language of the SyntaxEditor is set to Tsql the sql keywords are automatically converted to uppercase.
Is there a way to prevent this from happening?
I want to keep the coloring as it is.
I'm developing an application dealing with invoices and there are quite a few tables beginning with Order (OrderHistory, OrderItems etc).
For example OrderHistory:
The way it is now it first capitalizes OR so it first becomes: ORde
Then finally: ORDERhistory.
This is quite annoying and looks unprofessional.
Hello Dominik,
Thank you for posting tour forum.You just need to set 'AutoCasingMode' property of TextDocument to none.
Something like that :
this.SyntaxEditorTest.Document = new TextDocument() { AutoCasingMode=TextDocumentAutoCasingMode.None };
Also attached a sample application for your reference.
Please let me know if you need further assistance.
.EditorSample.zip
Hi,
I'm using 17.2.20172.1000 and I have this issue with TSqlLanguage, is there a flag I need to turn on?
Thanks,
Dominik
Hello,
This issue has now been resolved in the latest service release.
Sincerely,
Valerie
Developer Support Supervisor - XAML
Infragistics
www.infragistics.com/support
Hi Obrestad,
I created a private case for this issue and have link your case to the developer issue(126531).
You will be notified by email when this issue is resolved.
We already have an internal bug open for this issue in the VB language, which also has case-insensitive keywords (bug ID 126531). I have emailed the Developer Support manager to add you to this case. However, this is not likely to be fixed in an SR. Due to the nature of the bug, fixing it requires some new features which are not yet implemented in the parsing framework. So it will most likely be fixed in a newer version of the product. As a workaround, you can replace all TerminalSymbols having a Comparison value of LiteralIgnoreCase with equivalent symbols having a Comparison of RegularExpression. I have attached a sample to do this because it actually turns out to be quite complicated. Basically, with ignore case literals, we will correct the casing to match that of the original definition, but it is currently happening too early. It shouldn't happen until after the user leaves the word. Regular expression symbols don't have this issue because we don't know what the proper casing should be, so we always leave it as it was typed.