Case correction is too aggressive

[kpeters58]

I do use and appreciate PureBasic's case correction.

I often have longer strings that contain PureBasic keywords, such as 'for' and 'to', for instance.

The moment I edit one of these and overwrite/remove the leading double-quote (whether on purpose or accidentally), PureBasic immediately goes to work and uppercases such keywords.

In the best case that is annoying; in the worst case such improper spelling may end up in the hands of customers...

Maybe there is a way to suppress this behavior once a trailing doublequote is detected?

[Michael Vogel]

+1
Maybe strings shouldn't be changed before 'enter' will have been pressed (similar to some commands like "endif").
But it would be already a step forward, if the undo function would work to change the altered characters to it's prevoius state.

[dobro]

PureBasic immediately goes to work and uppercases such keywords.

if I understand what you write
not Purebasic putting keywords in uppercase
but is IDE

exchange your IDE

[IdeasVacuum]

...it possibly isn't that easy to fix, a number of IDE's have the same issue. Perhaps a button on the IDE to toggle case correction on-off? Or, perhaps better, case-correction only invoked by either Syntax Check or Compile.

[kenmo]

Yes, it can be annoying to modify a doublequote and suddenly every keyword in your string becomes capitalized (plus Undo does not undo case correction).

A workaround is to temporarily throw a ';' at the start of the line, to comment it out before modifying complex strings.

It might be better if the IDE only case-corrected words when you finish them (either by typing or auto-complete).