User forums > Using Code::Blocks

syntax highlighting question

<< < (2/3) > >>

Pecan:

--- Quote from: thomas on April 24, 2006, 08:51:02 pm ---After trying for a while, I've applied the patch for now, lacking a better solution (rev. 2376).
...
However, for the time being, commenting out that line certainly makes things better. With settings lost every time, the app is quite unusuable. Let's see if it fails, and why :)
...

--- End quote ---

Thank you. We all appreciate that. It's really been a pain in the @s.

thanks
pecan

Max:
Dear All,

Unfortunately the color setting is not the only "setting" that looses the modification. If you try to add a new keyword
the modification will be lost. I flagged this bug in the #7063, the bug was closed after the application of the Pecan's patch.

I have opened a new bug report (#7275) to flag the issue.

In the meantime I am adding the keyword manually in the .conf file.

Thanks

Massimo

Pecan:

--- Quote from: MaxGaspa on April 26, 2006, 12:34:59 pm ---Dear All,

Unfortunately the color setting is not the only "setting" that looses the modification. If you try to add a new keyword
the modification will be lost. I flagged this bug in the #7063, the bug was closed after the application of the Pecan's patch.

I have opened a new bug report (#7275) to flag the issue.

In the meantime I am adding the keyword manually in the .conf file.

Thanks

Massimo

--- End quote ---

Did you get a chance to test with the patch? It looked like,
to me, that the highlite bug was causing the keyword bug
also.

I was under the impression that the patch fixed both.

Not so???
 

Max:
Dear Pecan,

Yes, I am using the 2377, in which your patch was included. The bug is still present.

Try it. Open the editor setting -> Syntax Highlighting -> Keywords

In set 2 add a keyword

Click Ok and OK .


The new keyword is lost. It is not in the list as you can verify reopening the keyword dialog.

Massimo

Pecan:

--- Quote from: MaxGaspa on April 26, 2006, 07:07:41 pm ---You are so right. The problem is in a difference module altogether.
EditKeywordsDlg::OnSetChange() does not seem to be writing out the keywords.

I was wrong to associate my patch with this problem.

--- End quote ---

Well... as it turns out, the problem *is* in the same area as my patch.
But before I propose another patch, here's a little workaround that
you can use to set and save your keywords.

The trick is to change a highlite color before you exit the dialog.

1. add your keyword (maybe to set 2) but do *not* click on ok.
2. change the spin control to any other setting (maybe back to set 1)
3. now click on keyword dialog ok, but *not* on the full dialog ok
4. go change a color on something (maybe change UUID to grey)
5. now click on ok to exit the editor settings dialog

your keywords will be saved.
Sorry about the convoluted method. I'm sure it'll be fixed soon.

pecan

Navigation

[0] Message Index

[#] Next page

[*] Previous page