Prime Community Forum

Hello,

I am trying to use timeline component. I find when zooming in, the event could cross two rows. You can also check this problem with showcase.
http://www.primefaces.org/showcase-ext/ ... custom.jsf


Is it possible to avoid this? How to do that?

I am a newbie to front development. Can someone help to explain the reason?

Thanks a lot!

Ok, I see. Try to set "groupMinHeight" attribute. E.g. groupMinHeight="50".

From the docu: "The minimum height of each individual group even if they have no items. The group height is set as the greatest value between items height and the groupMinHeight. Default is 0."

@Oleg,

It works with groupMinHeight.
Thanks a lot!

I'm really surprised that the Primefaces showcases are still displaying such an obvious bug:

http://www.primefaces.org/showcase-ext/ ... 2ezpryzs9z

http://www.primefaces.org/showcase-ext/ ... custom.jsf

The main problem with using groupMinHeight is that you have to know the exact "normal" height of your timeline events to avoid any visible change of height when zooming in or out (if set too small), or any permanent change in height (if set too big). Also, this option is not recognised by older versions of Primefaces Extensions (we were using V2.00 before), meaning we cannot include this option as a future-proofing change. In fact, the older version of Primefaces Extensions seemed to be able to display the timeline properly without this problem occurring, so I am not convinced that this option is a proper solution to the problem.

The default resizing behaviour is clearly not desirable in any case - I cannot see why any user would ever want to see their events shifting up to different (incorrect) group members in the group when they zoon in, so I feel that this is definitely a bug which requires correcting in a future version.

Thinking about this a bit more, the problem isn't actually the dynamic re-sizing of the row height, rather the migration of the content from one row to another as a result, which is obviously incorrect and very misleading (if not downright dangerous) for the user. To me, this looks like a straightforward bug, and the adjustment of groupMinHeight is just masking the underlying problem.