Why are you opening the Custom Format page? Although that shouldn't cause a problem, you can set the Keyword and Identifiers case formatter options on the Format or Advanced Format pages.
Actually that was just an excursion on the quest for the lost option...
Even though thatJeffSmith-Oracle did not explicitly say "Change case as you type" was removed intentionally, it does make sense that having such a preference along with similar Format / Advanced Format options would be confusing and redundant.
And if you like, the Alt+Quote shortcut key is still available in 18.1's worksheet and code editor to toggle through all these case-related format options.
Opening [the Custom Format dialog] makes SQL Developer use all of the CPU so that I eventually have to kill the process.
Well, it does not for me on Windows 10.
The release notes cover this:
- Change Case as You Type was removed from the Code Insight Preferences page. Use the Code Formatter to set your identifier and keyword preferences, and format your code on demand instead.
Well, my bad, I should not have missed that. Thank you.
Now the only mystery is why does the OP experience high CPU over an extended period of time. In my case, even with Start Page and DB Instance viewer running, my system bounces between 15% - 40% CPU and 3% - 9% GPU (Intel, with 0% NVIDIA).
Mousing over other apps on the Windows Taskbar will cause GPU spikes, but nothing over 23%.
Sorry - didn't see that.
I found that option very useful and find it a bit clumsy to format code afterwards.
Regarding the CPU usage (and having read thatJeffSmith-Oracle's answer here https://community.oracle.com/thread/4129517#thread-message-14745424 ) - here's a stack dump on pastebin, just in case anyone's interested: https://pastebin.com/QQ8LaqWE
I know that, but isn't it easier to just hit <enter> than to go back, mark text and press <ctrl>-<quote>? (which, by the way, in my installation only turns upper or initial case to lower case and not vice versa, this only works in the context menu).
I'd like to fix the clumsy part. Hitting Ctrl+F7 after finishing your SQL isn't hard, so I'm guessing you don't like something that the formatter does to your code?
Hitting Ctrl+F7 after finishing your SQL isn't hard, so I'm guessing you don't like something that the formatter does to your code?
This is right. I find it pretty difficult to adjust the settings so that they totally fit my preferences - be it alignment, line breaks or whatever.
I once (in one of the previous versions) almost had it where I wanted, but the settings got lost with changing to a newer version.
And I was quite happy with hitting tabs during typing till the layout fit my personal idea of "aesthetically pleasing". So losing the ability to automagically get the case set "right" doesn't really make me happy.
I found that option very useful and find it a bit clumsy to format code afterwards. While writing, I can format the code easier and more readable. I have the version 17.4 reinstalled and hope that this function in whatever form will be available in the future again.
P.S. When I try to change the format settings, the processor load increases to 100% (Linux).
18.2 now has an option to only format case of reserved words and indentifiers if you don't like the rest of the formatting features.
I also somewhat miss the old behaviour (not that it was perfect either).
The formatter does not always do an ideal job so routinely reformatting everything is unrealistic.
Having to go to the preferences to switch between the occasional "flull-blown" reformating and "alter case only" is cumbersome.