designerInitialized inside a module have accumulative id's

designerInitialized inside a module have accumulative id's

Posted by: ricardo.aleixo on 24 August 2021, 2:03 pm EST

• 

  ricardo.aleixo

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 24 August 2021, 2:03 pm EST

  Hi.

  I have been working with spreadJS Designer, and our spread instance show a accummulative id.
  
  using

  <designer (designerInitialized)="getDesigner($event)" [props]="spreadConfig.props"></designer>

  this spread are render inside a modal, after work with it and close modal, i make the destoy(), but opening this modal again, instand of the id been interpreted like a new one. our Id are counting more and more, causing a slowet process.

  futher destoy method, we have another way to clean workbook, like evertime a new one?

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 25 August 2021, 1:25 am EST

  Hi Ricardo,

  I’m sorry but I’m unable to understand the issue, would you please explain what you mean by id counts are increasing?
  
  From the code snippet, it seems that you are using angular, for angular instead of calling destroy() you may use ngIf* to hide/show designer, and destroy and initialization work will be done by the framework properly on its own. You may refer to the attached sample demonstrating the same.
  
  designerv14-hideshowdesigner.zip

  ~ sharad

• 

  ricardo.aleixo

  • Post Options:
  • Link
    Copy

  Posted 14 October 2021, 9:01 am EST - Updated 3 October 2022, 9:35 am EST

  Testing your attach file, i saw the same behaivor that i have at: app.component.ts, i set a console.log:
  
  

  

  844×296 34.9 KB

  the result of these console is:

  

  1903×1035 151 KB

  These ‘ID’ that are increasing, are they a problem?

  because in my application, i thing this may cause a performance issue, or maybe i am wrong.

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 18 October 2021, 12:45 am EST

  The designerId property you mentioned is for internal use only. The increasing value of designerId property will not have any impact on the performance, you may simply ignore this value.
  
  Further, if you come across any performance issues, then do let us know and we shall investigate the issue accordingly.