[Lazarus] white flash when opening new unit while debugging

Martin lazarus at mfriebe.de
Sun Nov 8 20:05:18 CET 2009


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

Zaher Dirkey wrote:
> 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.
>
> On Sat, Nov 7, 2009 at 4:27 PM, Martin <lazarus at mfriebe.de> wrote:
>   
>> David Emerson wrote:
>>     
>>> 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.
>>>
>>>       
>> 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
>>
>>
>>
>> --
>> _______________________________________________
>> Lazarus mailing list
>> Lazarus at lists.lazarus.freepascal.org
>> http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
>>
>>     
>
>
>
>   





More information about the Lazarus mailing list