User forums > Nightly builds

The 27 October 2014 build (10016) is out.

<< < (5/13) > >>

oBFusCATed:

--- Quote from: ollydbg on November 02, 2014, 09:56:15 am ---It crashed when parsing class definition body, and I see macro expansion happens several times, but finally it crashed in m_TokenTree->TokenExists. If I see the crash in my system, I can debug it. But currently I can't.

--- End quote ---
This is not a crash, I've just stopped it to see what is doing.
It doesn't crash but what happens is probably that it enters an infinite loop of macro expansion.
I'll try to see if this is related to a single project or the order of evaluation of project breaks it.

ollydbg:

--- Quote from: ollydbg on November 02, 2014, 09:56:15 am ---

--- Quote from: oBFusCATed on November 01, 2014, 09:59:38 pm ---Another problem that is extremely annoying is that the value of the "Case sensitive matches" in the code completion settings is not save in the config file.
And I have to set it every time I start new instance of codeblocks.
Also why this is set to the non-obvious state on, I think this should be off by default.


--- End quote ---
It's a bug.
I did some test, if you open C::B (without opening any project), and just set the "Case sensitive matches", and close C::B, you will see those settings get saved.
But if you open C::B, and open one project, then set the "Case sensitive matches" option, and this options gets lost if you close C::B.
I will look into this.


--- End quote ---
Debugged a while, I found the reason why this bug happens, but I don't have a clean way to fix this issue.
See, the CC setting was stored in configure file.
When C::B start up, CC will create a default parser object called "temp parser".
When a parser object is created, it will copy the settings(such as the "Case sensitive matches") from the configure file to its own member variable.
When you open the CC dialog, the active parser object's setting will be modified also the CC related setting in configure files will get updated. This means, the configure file contains the active parser's settings.

When a CB project loaded, a new parser object(we call "new parser" here) is created and activated. So far, so good. When you changed the CC setting, both the "new parser"'s setting and the configure file get updated.

The issue comes when you close C::B, which means, you need to
1, destroy "new parser"
2, destroy "temp parser"

When destroy "new parser", all its setting was saved, but after that, the active parser switches to "temp parser", the setting in "temp parser" was active, and finally the "temp parser" get destroyed, its setting was saved (not the "new parser"), so your setting was lost!

I have not a good idea to fix this issue. Say, we have a setting shared by several parser objects. But they may be different, but the last destroyed parser's setting will be saved to the configure file.

oBFusCATed:
Just add a flag to the temp parser and prevent it from saving its settings.

pluto:
Hi :)
I've found some small issues that have been present for a few builds now. I'm currently using the build 10016 on Windows 7 32bit.
I'm not sure I should open tickets on SF for any these things. If I have, just tell me. I don't want to waste anyone's time :p

1) The Code Completion option "display info when hovering mouse over a token in the editor" is always active.
Even when uncheckd, it shows a tooltip. Plus it has wrong colors.

Ticketed here: https://sourceforge.net/p/codeblocks/tickets/88/

2) The mouse cursor on the left margin is not mirrored or showing the left-to-right arrow. In older versions of CB it worked like that if I'm not mistaken.

3) If I put the focus on one of the dockable windows (while docked), its titlebar changes to the focused color, and that's correct.
If then I click in the editor, the cursor shows up in the editor and I can type fine, but the docked titlebar still has the focused color. To get the unfocused color I have to click on the editor tab.
I don't know if it's simply a color problem or there is some orphan window selection of sorts.

4) I use a dark theme in Windows, and so it's very visible where CB mixes system colors with custom ones, and it's very unreadable ;p
here some examples (hope they show correctly):













5) The key bindings for the split and unsplit are missing

Thanks for reading :)

ollydbg:

--- Quote from: oBFusCATed on November 03, 2014, 12:13:28 am ---Just add a flag to the temp parser and prevent it from saving its settings.

--- End quote ---
Yes can be done easily, but cause another issue. If a user open C::B (with out any C::B project opened), and change some CC settings, those settings also get unsaved. :(

Navigation

[0] Message Index

[#] Next page

[*] Previous page