Hey everyone,

Since I've been asking a few questions now and then, I'd like to give a big thanks to everyone for your wonderful feedback and of course all the hard work! I hope to contribute someday when I am able.

On to the next question :)

I use an inverted color scheme, which helps me with a minor visual disability.

I often ctrl+click on an identifier to jump to its declaration. If the unit where the identifier is declared is not open, it is automatically opened for me. This is great!

As long as I am not debugging, everything looks great.

However, when I am debugging, the automatically opened unit is first rendered with a white background before my color scheme is applied. This results in a visually disturbing white flash.

Is this something I should formally report as a bug, or...?

Cheers,
~David.

Yes, please report as a bug.

This may not end up with the highest priority right now, but if you need a quick fix, you can modify synedit

line 1636 (within constructor SynEdit.create)
  Color := clWhite;

Change it to your preference, and recompile synedit and the ide

Thanks for the tip, Martin!

I did file a bug report.

I checked out the svn (actually used Graeme's git repo) made the change, compiled, and ran, and it seems not to have had any effect.

(Since it was my first time, I played around and verified that my changes were actually being incorporated.)

I also tried changing the default value where the property is declared, to no avail.

Cheers,
David

Martin wrote

Yes, please report as a bug. This may not end up with the highest priority right now, but if you

need

give a

the

> unit where the identifier is declared is not open, it is

automatically

In that case it is probably the underlying page of the notebook, that is displayed to you. (and which happens to be white too). I have to investigate at some time.

I know those things (various drawing/display effects) happen when the debugger is active. I assume this to be, because the debugger does calls to Application.ProcessMessages (which is required). That means that paint events come in early.

Sorry no quick fix then.

Martin

This also not in Debug mode, some time in normal state, there is a flicker by white background and black font in editor and the tab not take the real name of the unit, it changed to the correct name with applying the color themes.

I think (but not sure) it is around the source editor in IDE not related directly to SynEdit.

Thanks for your patience.

I've done a bit more looking into it.

The problem is that6 SynEdit is shown, when the notebook tab is changed (which will be hard to avoid).
At this time it is an empty SynEdit, with no highlighter.

and an SynEdit with no highlighter currently uses default, none configurable colors.

They are defined in  ide\editoroptions.pp (and not in synedit as I
thought first)
in:   procedure TEditorOptions.SetMarkupColors(Syn: TSrcIDEHighlighter;
aSynEd: TSynEdit;
Line 3668:
  if (SynColorScheme  '') then begin
.....
  end
  else begin
    aSynEd.Color := clWhite;
    aSynEd.Font.Color := clBlack;
  end;

aSynedit.Color is what you need to change.

-------
Not tested, but pretty sure.

Martin