Since the last time I rebooted my computer, Code::Blocks would frequently hang even if I did nothing after launching it.What do you mean by hang (crash to desktop or the UI is unresponsive)? Which version is doing this?
Disabling all plugins did not help, and attempting to disable the Threaded Search plugin would immediately result in the program crashing. I ended up moving the DLL from the plugins folder as a workaround. I'd mostly been using 17.12 due to some documented bugs regarding the IDE's use in a Remote Desktop session (http://forums.codeblocks.org/index.php/topic,23498.msg160045.html#msg160045), but if I can't use it at all I'm forced to upgrade or just reboot again and hope for better results. Downloading this latest nightly, I checked the plugins, and everything was disabled except threaded search, and likewise trying to disable it there results in the program crashing. Is this a known bug? Is there a workaround other than to delete/move the DLL for it? Is there any troubleshooting I can do or do I just have to give up on 17.12?ThreadSearch unloading crash is known, I've fixing it but I've god distracted... I will do it soon.
Edit: There's also some strange issue with this nightly where selecting text does not draw a background to reflect that it is highlighted. Is there a simple fix for this?First time I hear about this I think. Remote desktop or normal desktop? Does it happen with the previous night builds?
Also, about 3/4 a year ago, it was suggested that the font used in "Logs & others" may be chosen automatically by wx and my findings is that it changes depending on the OS's defined locale. Had anything changed to where I could actually change it to Courier New (which can be configured in the Editor settings)?Nope you can only change the size of the font...
Since the last time I rebooted my computer, Code::Blocks would frequently hang even if I did nothing after launching it. Disabling all plugins did not help, and attempting to disable the Threaded Search plugin would immediately result in the program crashing. I ended up moving the DLL from the plugins folder as a workaround. I'd mostly been using 17.12 due to some documented bugs regarding the IDE's use in a Remote Desktop session (http://forums.codeblocks.org/index.php/topic,23498.msg160045.html#msg160045), but if I can't use it at all I'm forced to upgrade or just reboot again and hope for better results.I am now in the position to make a RDP connection between two windows pc and debug this issue. Can you open a Ticket on SF and describe the exact steps to reproduce the crashes (with wxWidgets versions and codeblocks versions)? Please describe in detail, because i never used RDP (is it something like X forwarding?) on windows. It is quite difficult to read trough all the forum posts and it would be nice to have all information in one Ticket.... Then i can try to fix this. Thank you for your patience.
What do you mean by hang (crash to desktop or the UI is unresponsive)? Which version is doing this?UI hangs indefinitely (possibly forever) and Windows says it isn't responding. I could attach a debugger on the release made here but as per my previous posts, my version of MinGW is incapable of building from source so I can't build with debugging symbols and my backtrace may be useless to you.
Can you attach a debugger and show backtrace for all threads of a hanged process? It might give us a clue which function/dll is doing this.
First time I hear about this I think. Remote desktop or normal desktop? Does it happen with the previous night builds?I didn't use the previous couple nightly builds much because of the RDP problems, but the selected text missing background coloration issue was when launching and using C::B in person. Speaking of the RDP issue, my C::B session I left running crashed when I RDP'd into the machine today. Relaunching this nightly within an RDP session results in the same assertion failures that I can continue past, and at least during this session I'm not seeing the selected text coloration bug. I'll have to see what happens when I use it again in person later.
I am now in the position to make a RDP connection between two windows pc and debug this issue. Can you open a Ticket on SF and describe the exact steps to reproduce the crashes (with wxWidgets versions and codeblocks versions)? Please describe in detail, because i never used RDP (is it something like X forwarding?) on windows. It is quite difficult to read trough all the forum posts and it would be nice to have all information in one Ticket.... Then i can try to fix this. Thank you for your patience.I created a ticket:
I've done some changes to this recently and I might have broken something (or exposed another bug).I'm guessing you want the default.conf file? I've attached that (when the default selection background is selected and is white on a white editor background), but if that's the wrong file, please let me know.
Can you attach one broken config file (I don't think there is sensitive info in it, but if you're afraid to attach it, you can send me a pm)?
I don't see this. Can someone else on windows try to reproduce this?I can not reproduce it normally: i have tried to do Settings->Editor->Syntax highlighting->Reset defaults . After this still all seems to be normal
void EditorConfigurationDlg::OnSetDefaultColour(wxCommandEvent& event)
{
wxWindow *button = nullptr;
if (event.GetId() == XRCID("btnForeSetDefault"))
button = FindWindowById(XRCID("btnColoursFore"));
else if (event.GetId() == XRCID("btnBackSetDefault"))
button = FindWindowById(XRCID("btnColoursBack"));
if (!button)
return;
button->SetBackgroundColour(wxSystemSettings::GetColour(wxSYS_COLOUR_BTNFACE));
button->SetLabel(_("\"Default\""));
WriteColours();
}