Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Two problems with r8232
oBFusCATed:
I've just updated to r8232 and there are two problems:
1. Suddenly the default color for everything is gray instead of black. I don't know why this happens, but I've not modified colors in the 2-3 year or at all.
The preview in the syntax highlight settings panel looks correct. Also removing the default.conf makes this problem go away.
2. Just tested to remove the default.conf file and I've got a pleasant red surprise:
I have no time to investigate what is causing this issues, so I'll be happy if someone does it for me :-P
My previous revision was 8164.
p.s. do we need to store the recent file/project list in the default.conf file? Should this is save in another file?
Alpha:
--- Quote from: oBFusCATed on August 13, 2012, 10:57:24 pm ---1. Suddenly the default color for everything is gray instead of black. I don't know why this happens, but I've not modified colors in the 2-3 year or at all.
--- End quote ---
Sorry, I really need to stop messing with the lexer :). I rev8230 shifts many of the items in the C/C++ lexer, so if the default.conf has any saved color schemes, it is unlikely to load them correctly. (PS: try the new check boxes under C++ editor settings.)
--- Quote from: oBFusCATed on August 13, 2012, 10:57:24 pm ---2. Just tested to remove the default.conf file and I've got a pleasant red surprise:
--- End quote ---
Code::Blocks always highlights items in red if at the point of loading, their master paths are empty (which they all are when a new profile is started).
In the XML compiler branch, this dialog has been modified so that (among other things) detected compilers are not erroneously highlighted.
oBFusCATed:
--- Quote from: Alpha on August 14, 2012, 12:43:52 am ---Sorry, I really need to stop messing with the lexer :). I rev8230 shifts many of the items in the C/C++ lexer, so if the default.conf has any saved color schemes, it is unlikely to load them correctly. (PS: try the new check boxes under C++ editor settings.)
--- End quote ---
I don't know the details, but you must make sure that current profiles work as before or we will get tons of people complaining about it!
--- Quote from: oBFusCATed on August 13, 2012, 10:57:24 pm ---Code::Blocks always highlights items in red if at the point of loading, their master paths are empty (which they all are when a new profile is started).
In the XML compiler branch, this dialog has been modified so that (among other things) detected compilers are not erroneously highlighted.
--- End quote ---
Is this (the red backgrounds) some new feature as I've never seen in before?
I don't think this is something that is user friendly, so it needs to be fixed or at least it needs to be made a bit less disturbing and a bit more clear.
Alpha:
--- Quote from: oBFusCATed on August 14, 2012, 12:52:25 am ---
--- Quote from: Alpha on August 14, 2012, 12:43:52 am ---Sorry, I really need to stop messing with the lexer :). I rev8230 shifts many of the items in the C/C++ lexer, so if the default.conf has any saved color schemes, it is unlikely to load them correctly. (PS: try the new check boxes under C++ editor settings.)
--- End quote ---
I don't know the details, but you must make sure that current profiles work as before or we will get tons of people complaining about it!
--- End quote ---
I will explore it to see if there is anything that can be done, however to my current knowledge, the way custom color schemes are saved would make this extremely difficult to create an automatic upgrade. (I could be wrong on this.)
--- Quote from: oBFusCATed on August 14, 2012, 12:52:25 am ---Is this (the red backgrounds) some new feature as I've never seen in before?
I don't think this is something that is user friendly, so it needs to be fixed or at least it needs to be made a bit less disturbing and a bit more clear.
--- End quote ---
It has been in there at least since the last stable (two years ago), and probably longer. The modifications in the XML compiler branch are a little more friendly; even there, however, more needs to be done...
Alpha:
sdk/editorcolourset.cpp, line 521
--- Code: --- for (OptionSetsMap::iterator it = m_Sets.begin(); it != m_Sets.end(); ++it)
{
if (it->first == HL_NONE || it->first == HL_AUTO)
continue;
wxString lang = it->first;
bool gsaved = false;
key.Clear();
key << _T("/colour_sets/") << m_Name << _T('/') << lang;
for (unsigned int i = 0; i < it->second.m_Colours.GetCount(); ++i)
{
OptionColour* opt = it->second.m_Colours.Item(i);
wxString tmpKey;
tmpKey << key << _T("/style") << wxString::Format(_T("%d"), i); // <-- how can something saved numerically be auto-magically updated?
[...]
--- End code ---
Navigation
[0] Message Index
[#] Next page
Go to full version