Question: Preventing auto correct spelling of KeyWords

[Stefan]

Question: Preventing auto correct spelling of KeyWords

My settings:
Case correction: Make operant = [Like in Syntax definition  ][v]


If i wrote code
the keywords like 'for'
are expanded to correct spelling 'For', ... that's good.

Problem:
But if i wrote comments or "strings"
those "for, name, to, file" are corrected to "For, Name, To, File" too, this disturbs.

Question:
How can i disable this auto correct spelling on the fly?


Suggestion:
Maybe new command/button/shortcut to toggle  "Make operant: use last setting" / "Make operant: use As Typed" ?

?

[alex]

Hi Stefan,

the keywords should not be auto corrected with "Case correction" inside of string or comment blocks. This action is style dependent and would be only applied in the document parts where keywords are allowed.
I see too possible reasons for this:
- some other smart feature executed and word was corrected
- you found some bug, which I could not reproduce. Then please describe step by step how to reproduce the error.

Best regards,
Alex.

[Stefan]

> This action is style dependent

Ups, i see,
so i have to tweak my syntax scheme (a copy of VB scheme adopted for an own AutoHotkey scheme)

But AHK didn't need "..." around an string,
the string is just an parameter, coma separated behind an keyword, f.ex.:

MsgBox,,Title,  %A_WorkingDir%\%AppName%.exe missing. Script ends here.

Any hint how i can set this up... 

An comment looks like
;comment here
so i guess this should work. I will test this.

---

On the other side i want to wrote un-corrected text
which is not an string or an comment,
like with Example2 below.

myHelp =
(
Enter path and File Name
or chose an recent ini fro
or browse For path and fi
or create new ini File => [
)
Gui, Add, Text,    , %myHelp%

[alex]

Hi Stefan,

yes... this is complex. As partial workaround, you can create new syntax style, started with MsgBox and ending with end of line \n. And then define what (which other styles) should be inside. 

But this is only partial workaround. Of course, I can think about adding of the command for disabling of case correction, but there are much more other actions which would work wrong in such cases as: templates, code hints, highlighting, completion etc...

For me currently is not clear what can be a correct way here. I/we can think about this and decide what to do later...

Best regards,
Alex.