Setting row expandable in Far Point Spread

Setting row expandable in Far Point Spread

Posted by: kerenb on 11 December 2018, 4:53 am EST

• 

  kerenb

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 11 December 2018, 4:53 am EST

  Hello
  
  I have tried many options including a sample snippet to add a data set to the DataSource of a FarPoint.Win.Spread but with no success. It doesn’t show the + sign.
  
  Please help
  
  Thanx Keren

• 

  kerenb

  • Post Options:
  • Link
    Copy

  Posted 11 December 2018, 7:00 am EST

  There is progress
  
  I have found that the designer adds automatically two definitions
  
  one for FpSpread and one for SheetView

  private FarPoint.Win.Spread.SheetView fpBelongingToMadadSpread1;
  
  private FarPoint.Win.Spread.FpSpread fpSpreadIssuedDetails;

  Only when i comment out the SheetView from the designer file it shows expand rows correctly with a + sign

  Why is that?

• 

  reeva.dhingra

  

  • Post Options:
  • Link
    Copy

  Posted 12 December 2018, 5:59 am EST

  Hello,

  With Spread latest version V12, we are unable to replicate the issue wherein in hierarchical view we are getting + sign in row headers to expand the rows.

  However, if you will set setRowExpandable(rowindex, false) property to false then it will not show + sign in that row(with specific rowindex)

  Please have a look at attached row and let us know what are we missing to replicate the issue and also share your Spread version.

  You can modify our attached sample to replicate the issue and revert. We will look into the same thereon.

  Thanks,
  
  Reeva
  
  SpreadWin_hierarchical.zip

• 

  kerenb

  • Post Options:
  • Link
    Copy

  Posted 17 December 2018, 3:01 am EST

  Thank you
  
  I have managed to solve it
  
  and for rows that are not expandable i run the function setRowExpandable with false
  
  thank you

• 

  reeva.dhingra

  

  • Post Options:
  • Link
    Copy

  Posted 18 December 2018, 12:02 am EST

  Hello,

  We are glad to know that your issue has been resolved.

  Thanks,
  
  Reeva