Issue 691: Min-height for agenda events. Render events by computed height
Status:  ExportedToGithub
Owner: ----
Closed:  Aug 2015
Reported by russell....@googlemail.com, Oct 29, 2010
Can you add a "Minimum event height" option to stop the events becoming too thin to read?  I've got events in my calendar that are only 5 minutes long and they appear as 4 pixel tall boxes with no text in them.  It would be great if they stopped shrinking at about 15 pixels so the title was still visible.

Thanks

Russell
Nov 10, 2010
Project Member #1 althaus.it
You can achieve this through CSS:

.fc-event-vert {
  min-height: 25px;
}
Nov 10, 2010
#2 dbrat...@gmail.com
Setting minimum height using css does not work properly with multiple short events that almost overlap each other. If you have one event at 09:00 with 5 minutes duration and another one at 09:05 with 5 minutes duration, then fullcal does not think that they overlap, but with the css rule above, they will overlap and one event will cover the other one.
Nov 21, 2010
Project Member #3 adamrs...@gmail.com
i would really like to keep this appearance-related stuff in CSS, but i understand why it is not working in this case. will think this one over. to make it work, would probably need to rewrite the way agenda events are rendered.
Summary: New technique for rendering agenda events (consider computed height)
Status: Maybe
Sep 7, 2012
#4 schlur...@googlemail.com
Hi,

I would like to see this feature implemented too. We are facing the same problem here. For example, if you are trying to use fullcalendar as a scheduler for movies and commercial clips. When adding clips, the events are only rendered as a very thin line. We tried using the 'min-height'-css-option, but as already said, multiple short events are overlapping each other.

Any suggestions for another solution or a workaround is more than welcome.
Aug 13, 2013
Project Member #5 adamrs...@gmail.com
(No comment was entered for this change.)
Status: Accepted
Labels: -Type-Enhancement Type-BehaviorMod
Aug 14, 2013
Project Member #6 adamrs...@gmail.com
There are two issues at work here:

- setting a min-height for events. it should probably default to 1 or 2 "slots", which needs to computed in the JS, but we should allow for a user's stylesheet to manipulate the height too

- render agenda events based off of their computed heights (like basic view)
Summary: Min-height for agenda events. Render events by computed height (was: New technique for rendering agenda events (consider computed height))
Labels: -Type-BehaviorMod Type-Behavior
Oct 30, 2013
#7 grant.je...@gmail.com
The fix by Dominik in  issue 1065  worked better for me. Adding the Math.max function keeps the slot a min-height and displays events with out overlapping them on top of each other.
Jul 17, 2014
Project Member #8 adamrs...@gmail.com
 Issue 2209  has been merged into this issue.
Jul 17, 2014
#9 sundar.soul
Hi Adamrs, 

Is there any update on the above one, It would be really help full to us. 

Looking forward for your reply 

Regards,
Racer.
Oct 15, 2014
#10 sundar.soul
@adamrs,

Any update on this?. If possible will be more helpful.
Nov 5, 2014
#11 drrichar...@gmail.com
I wanted this to have the min height = slot interval so I used:
Afer:
top = timePosition(seg.start, seg.start);
bottom = timePosition(seg.start, seg.end);
Add:
intervalHeight = timePosition(seg.start, addMinutes(cloneDate(seg.start),opt('slotMinutes'))) - top;
THEN
Change:
seg.outerHeight = bottom - top;
To:
seg.outerHeight = Math.max(bottom - top, intervalHeight);

Nov 24, 2014
#12 sorathiy...@gmail.com
Thank You @drrichar.

I used your trick and it worked. I also would like to know , Is it possible to stop event overlapping with event's minimum height? It should adjust the width of overlapping events.

Please find the attached images.
Looking forward to receive your suggestion.


  
expected output.PNG
20.0 KB   View   Download
Apr 19, 2015
Project Member #13 adamrs...@gmail.com
(No comment was entered for this change.)
Labels: -Type-Behavior Type-Feature
Aug 21, 2015
Project Member #14 adamrs...@gmail.com
Discussion for this issue has moved to the following URL:
https://github.com/fullcalendar/fullcalendar/issues/961

This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event.

Happy coding,
Adam
Status: ExportedToGithub