Spellcheck not work:
I am working on it. He provided example files here http://forums.codeblocks.org/index.php/topic,23102.msg157663.html#msg157663Spellcheck not work:
Khram refuses to supply requested information.
Tim S.
It's very nice to see the void casting bug fixed in this release. I don't immediately see that Hunspell is actually included with Firefox 65.x on Windows, it seems to ship with a different kind of dictionary as there is no dictionary folder in the browser's install folder, and nothing obviously relevant in my Firefox profile folder. Manually installing the Hunspell dictionary plugin for Firefox (https://addons.mozilla.org/en-US/firefox/addon/us-english-dictionary/) didn't provide something that is obviously (to me) usable in C::B. Is there some no-effort way to get the spell checker going like it was out-of-the-box in older nightly builds?My codeblocks finds the dictionaries from libre office and works out of the box
Is installing Open/Libre Office the lowest effort way to get a compatible Hunspell install then?
or build Hunspell from sourceWhy would you want to build hunspell from source? The only thing you need are dictionaries. Codeblocks provides the binaries, but not the dictionaries... You can download from here https://github.com/wooorm/dictionaries , or you download the dictionary extensions from libre office or open office, extract them like a zip archive and only use the dictionaries from inside them, no need to install some office suite...
Will the spell checker be included by default in future full releases?The spell checker should be included by default (if nothing went wrong with this nightly, i did no checked it) but you have to provide the dictionary for your language, as it always was...
Continuing to click Continue just repeatedly alternates between these two messages, possibly indefinitely, until stop is clicked and the program is allowed to crash.On linux there is a checkbox to ignore further asserts of this type. Isn't this the case on windows?
insert/refractor don't work :'(Works fine for me on Windows 10 Pro 64bits.
There's a "don't show this dialog again" checkbox in the Windows release, I just didn't want to use that if it would suppress the message even in future launches of the program (in case I could help troubleshoot).This is not something that is preserved between launches.
I found that if I did click Continue 34 times it did get into the IDE eventually.Can you try to disable some plugins to try to find if it is a plugin causing these asserts?
# Should __WXDEBUG__ be defined? The default value "default" means that it will
# be defined if BUILD=debug and not defined if BUILD=release. [0,1,default]
DEBUG_FLAG ?= default
# Value of wxDEBUG_LEVEL. The default value is the same as 1 and means that all
# but expensive assert checks are enabled, use 0 to completely remove debugging
# code. [0,1,default]
DEBUG_FLAG ?= 1
Should I put an enhancement request on the bug tracker about a way to list all words flagged by the spell checker? Having the option to sort this list would also be very handy so I could ignore variable names and look for truly misspelled words.Yes... But if someone would implement it is another matter...
The Fortran Project crash has the same origin (use-after-free), but in this case the solution is easy: remove the call to Destroy() in FortranProject::RemoveLogWindow(bool appShutDown). I will try to report this to Darmar.