Castalia’s block highlighting doesn’t treat blocks nice if the indentation doesn’t follow the standard alignments.

Castalia’s block highlighting doesn’t treat blocks nice if the indentation doesn’t follow the standard alignments. Very annoying for us that have different habits.

It could have worked if it didn’t insist on starting at the position of the begin/try, but rather on the first non whitespace at the line that contains the begin or try.

 

XE8 Findings

XE8 Findings

Found some minor tweaks in XE8. Will add to this post as I find more.

Breaking changes in FireDAC.UI.Intf

TFDScriptOutputKind used to be TFDScriptOuputKind

I actually QPd this, so blame me 😛

Breaking changes in FireDAC.comp.client

TFDConnectionLoginEvent = procedure (AConnection: TFDCustomConnection; AParams: TFDConnectionDefParams) of object;

used to be

TFDConnectionLoginEvent = procedure (AConnection: TFDCustomConnection; const AConnectionDef: IFDStanConnectionDef);

TFDErrorEvent = procedure (ASender, AInitiator: TObject; var AException: Exception) of object;

used to be

TFDErrorEvent = procedure (ASender: TObject; const AInitiator: IFDStanObject; var AException: Exception) of object;

TFDConnectionRecoverEvent = procedure (ASender, AInitiator: TObject; AException: Exception; var AAction: TFDPhysConnectionRecoverAction) of object;

used to be

TFDConnectionRecoverEvent = procedure (ASender: TObject; const AInitiator: IFDStanObject; AException: Exception; var AAction: TFDPhysConnectionRecoverAction) of object;

This one as a bit annoying as I actually was accessing the IFDStanObject.Name property.  I guess .classname will have to do.