Can't specify the wijmo flexgrid detail height

Can't specify the wijmo flexgrid detail height

Posted by: antonbubel26 on 9 August 2019, 4:54 am EST

• 

  antonbubel26

  • Post Options:
  • Link
    Copy

  Posted 9 August 2019, 4:54 am EST

  Hello!

  I can’t figure out how to set the wijmo flexgrid detail height. It always set to 42px and in the flexGridDetailProvider there is only one property that specifies the max height, but this isn’t working either.

  I’ve tried to add row detail using detailProvider and by using an ng-template with the wjFlexGridDetail directive on it and both solutions are not working.

  I can see that the detail under the row has an absolute position, then the other row underneath it with an absolute position as well, so I can’t process it using css it has to deal with wijmo itself.

  We’re using an angular cli version 7.1.0 and wijmo version is 5.20183.568-rc.

  Thank you!

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 11 August 2019, 5:30 pm EST

  Hi Anton,

  By default, FlexGridDetailProvider sets the height of the detail row enough to wrap it content. So if you want to give a fixed height to the detail cell, then you may simply wrap your detail content in a div element and specify height on it. Please refer to the following code snippet and the sample demonstrating the same:

  <ng-template wjFlexGridDetail #dp="wjFlexGridDetail">
      <div style="height: 100px">
        <span>Some details</span>
      </div>
    </ng-template>
  

  https://stackblitz.com/edit/angular-wzztev?file=src/app/app.component.ts

  Regards

• 

  antonbubel26

  • Post Options:
  • Link
    Copy

  Posted 11 August 2019, 9:59 pm EST

  Thank you for your reply!

  The issue, I have mentioned, solved by upgrading the wijmo package version to 5.20192.624, for some reason we had an rc version installed: 5.20183.568-rc, in the release version 5.20183.568 the issue is still reproducing on our side, but when I’ve updated the package to the latest release version it has disappeared. I don’t know what has caused it to appear, but I’m happy with the issue being gone on the latest version.

  Thank you!

• 

  ashwin.saxena

  

  • Post Options:
  • Link
    Copy

  Posted 12 August 2019, 4:13 pm EST

  Hi Anton,

  We were not able to replicate the issue in the build version 5.20183.568 but we are glad that your issue is resolved by upgrading. Let us know if you face any queries.

  Regards,
  
  Ashwin