SiComponents Forums

Posted: **Fri Sep 27, 2013 8:28 pm**

Hi SiComponents

It seems my last post was deleted, was something wrong with it ?
Anyway I try again:

I use TSiLang 7.0.
Since Delphi XE4 I, and as it seems others as well, have weird problems with the Delphi IDE doing stack overflows (see QC#116583, QC#116629, QC#118669, QC#119321 in embarcadero quality central).

While looking for a workaround, I found that if I remove the code shown below in the initialization section of siComp.pas, the problem disappears in the IDE.
Because I do not understand this code, nor what this is required for, my question would be if I could safely deactivate it for design-time component ?
Of course I would leave it in for run-time.
Or what would I break if I am doing this ?

Code: Select all

initialization
  {$IFDEF DELPHI6}
  StartClassGroup(TComponent);
  ActivateClassGroup(TComponent);
  GroupDescendentsWith(TsiCustomLang, TComponent);
  {$IFNDEF FMX}
  { TODO : Port to FMX }
  GroupDescendentsWith(TsiFormStorage, TComponent);
  {$ENDIF}
  GroupDescendentsWith(TsiLangDispatcher, TComponent);
  {$ENDIF}

Thanks in advance for your help

Posted: **Mon Sep 30, 2013 6:46 am**

Hi,

Sorry for the missed topic. We're moving from server to server these days and it is possible that some database were not updated while moving to another server. This code is needed in order to "let know" IDE which classes could be used under different frameworks, like VCL, FMX and so on. So I guess this is needed.

SiComponents Forums

TSiLang: is this code required while design time ?

TSiLang: is this code required while design time ?