Author Topic: Possible bug? (merged cell issues)  (Read 2326 times)

ntoscano

  • Pro OEM
  • Newbie
  • *
  • Posts: 6
    • View Profile
Possible bug? (merged cell issues)
« on: November 02, 2016, 01:55:24 am »
Hello, I was playing with the merged cell example found here: http://paramquery.com/pro/demos/merge_colspan, and I noticed something strange.

The first merged cell area is {r1: 0, c1: 2, rc: 4, cc: 5 }, but if you look at the UI, the there are only 4 columns merged.
When I set 'cc' to 4, there were only 3 columns merged.
When I set 'cc' to 3, there were only 2 columns merged.
But when I set 'cc' to 2, there was no change, i.e. there were 2 merged columns.
and when I set 'cc' to 1, there was only 1 column of merged cells.

Can you guys explain the logic of the 'cc' option?

paramvir

  • Administrator
  • Hero Member
  • *****
  • Posts: 6310
    • View Profile
Re: Possible bug? (merged cell issues)
« Reply #1 on: November 02, 2016, 07:06:05 am »
This is normal and expected behavior of merged cells.

cc is original colspan of a merged cell, but if there is one or more intermediate hidden columns, visible/effective colspan gets reduced by same amount.

In the above example, "E" column is hidden, that's why the visible colspan is less.

Hope it answers your concern.

ntoscano

  • Pro OEM
  • Newbie
  • *
  • Posts: 6
    • View Profile
Re: Possible bug? (merged cell issues)
« Reply #2 on: November 02, 2016, 11:56:38 pm »
Thanks a bunch, that answers my question.