Author Topic: ConfigManager editor bugs  (Read 8637 times)

takeshimiya

  • Guest
ConfigManager editor bugs
« on: November 24, 2005, 09:06:16 pm »
Hi! It seems that the new ConfigManager will requiere
heavy testing. I've just noticed in latest CVS some bugs:

The first, the colors chosed in
Settings->Editor->Colors gets screwed up when saved to
the xml.

Here's the patch:
In sdk/configmanager.cpp at line 694, change
ret->Set(r, b, g);
to
ret->Set(r, g, b);


The second
, the <UNDERLINED bool="0" /> doesn't get
saved in some cases.

Take for example in C/C++ the Matching Brace Highlight.
Bold and Italic seems to get saved right, but despite you set to off the Underlined, it doesn't even get writted to the xml.
It gets writted if Underlined=1 though.

I suppose the bug is in some Save function from sdk/editorcolorset.cpp.

Hope this helps!

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: ConfigManager editor bugs
« Reply #1 on: November 24, 2005, 09:19:45 pm »
Hopefully, I 've fixed them all earlier today.
Thanks :)
Be patient!
This bug will be fixed soon...

takeshimiya

  • Guest
Re: ConfigManager editor bugs
« Reply #2 on: November 24, 2005, 09:54:27 pm »
 :D

Offline Urxae

  • Regular
  • ***
  • Posts: 376
Re: ConfigManager editor bugs
« Reply #3 on: November 25, 2005, 01:56:57 am »
The second, the <UNDERLINED bool="0" /> doesn't get
saved in some cases.

Take for example in C/C++ the Matching Brace Highlight.
Bold and Italic seems to get saved right, but despite you set to off the Underlined, it doesn't even get writted to the xml.
It gets writted if Underlined=1 though.

I suppose the bug is in some Save function from sdk/editorcolorset.cpp.

Hopefully, I 've fixed them all earlier today.
Thanks :)

If that one's fixed, feel free to close this bugreport I filed for it.

Now excuse me while I recompile from CVS and finally turn the bloody matching brace underline OFF ;).
« Last Edit: November 25, 2005, 02:10:42 am by Urxae »

takeshimiya

  • Guest
Re: ConfigManager editor bugs
« Reply #4 on: November 25, 2005, 02:27:28 am »
Oops, I didn't noticed that bug report.

BTW, I compiled recently the CVS and now I get zero syntax highlighting for any language. I hope this is because anon CVS lags.
I wonder if anonymous SVN from BerliOS will lag too...

Offline Urxae

  • Regular
  • ***
  • Posts: 376
Re: ConfigManager editor bugs
« Reply #5 on: November 25, 2005, 03:31:55 am »
BTW, I compiled recently the CVS and now I get zero syntax highlighting for any language. I hope this is because anon CVS lags.
Yes, I have the same problem. But I was able to turn off the underlining and put back the old C::B version (I archived it). Now as long as I don't touch the settings it should stay un-underlined :).

Quote
I wonder if anonymous SVN from BerliOS will lag too...
I think the lag is a Sourceforge-only thing. High traffic loads and such. Not sure though.

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: ConfigManager editor bugs
« Reply #6 on: November 25, 2005, 09:53:37 am »
BTW, I compiled recently the CVS and now I get zero syntax highlighting for any language. I hope this is because anon CVS lags.

Unfortunately not. I uncommented one line and didn't notice a typo in there, result of a copy-paste when converting to new ConfigManager, which caused this.
Fixed now in CVS.
I also fixed resetting colors to defaults. It would reset colors for all languages instead for the selected only (as is hinted by the question message box).
Be patient!
This bug will be fixed soon...

Offline Urxae

  • Regular
  • ***
  • Posts: 376
Re: ConfigManager editor bugs
« Reply #7 on: November 25, 2005, 10:53:28 am »
By the way, is there any way it can remember which language I had last selected and open that one when the dialog is created? It's rather annoying to have to switch from AngelScript to C/C++ every time, when that's all I program in lately.

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: ConfigManager editor bugs
« Reply #8 on: November 25, 2005, 11:00:33 am »
By the way, is there any way it can remember which language I had last selected and open that one when the dialog is created? It's rather annoying to have to switch from AngelScript to C/C++ every time, when that's all I program in lately.

 :)
Yes, but I just stopped commiting changes. It will have to wait till after the move is complete.
Be patient!
This bug will be fixed soon...

Offline Urxae

  • Regular
  • ***
  • Posts: 376
Re: ConfigManager editor bugs
« Reply #9 on: November 25, 2005, 11:36:22 am »
By the way, is there any way it can remember which language I had last selected and open that one when the dialog is created? It's rather annoying to have to switch from AngelScript to C/C++ every time, when that's all I program in lately.

 :)
Yes, but I just stopped commiting changes. It will have to wait till after the move is complete.
Submitted a feature request as a reminder: [ 1366192 ]

takeshimiya

  • Guest
Re: ConfigManager editor bugs
« Reply #10 on: November 25, 2005, 01:02:11 pm »
Urxae: I was just about to submit the request for that feature :shock:

I had it written even various days ago:

Actual behaviour:
    In the Settings->Editor->Color, the last "Color Theme" used gets saved but the
    "Syntax highlighting for" no. And gets a little annoying when you are testing how the colors
    look in "C/C++" for example, and nVidia cg gets selected.
Expected behaviour:
    Just save as a configuration the "Syntax highlighting for", and perhaps the last type selected
    also (a comment, number, etc)

Offline Urxae

  • Regular
  • ***
  • Posts: 376
Re: ConfigManager editor bugs
« Reply #11 on: November 25, 2005, 02:00:04 pm »
Urxae: I was just about to submit the request for that feature :shock:
Great minds... :D

Quote
I had it written even various days ago:

Actual behaviour:
    In the Settings->Editor->Color, the last "Color Theme" used gets saved but the
    "Syntax highlighting for" no. And gets a little annoying when you are testing how the colors
    look in "C/C++" for example, and nVidia cg gets selected.
Expected behaviour:
    Just save as a configuration the "Syntax highlighting for", and perhaps the last type selected
    also (a comment, number, etc)
Ah, so it was you that anonymously added that text as a comment?
Though I always get Angelscript as the default selection.

takeshimiya

  • Guest
Re: ConfigManager editor bugs
« Reply #12 on: November 25, 2005, 04:47:12 pm »
Hehe, as I said, I had written the text like 2 weeks ago, when the AngelScript support wasn't there, and nVidia CG was first :)

In fact, I have a big list of text of my feature requests/bugs waiting in my HD :D
« Last Edit: November 25, 2005, 04:49:45 pm by Takeshi Miya »