Multi-days event

[addy87]

Hello! I'm having some trouble with an event that last over 24 hours. I cannot set the <duration> value over 24 (Network I/O problem: parse error. Invalid int value for HourOfDay).

How can I achieve this?

I tried to split an event in 2 days like this:

<day date="2019-11-15">
<room name="ABC">
<title>Eventname1</title>
<event id="5f76dc3808c8677ca3515213db89291ecaca9b2dbf3e6">
<start>10:00</start>
<duration>14:00</duration>
</event>
</room>
</day>

<day date="2019-11-16">
<room name="ABC">
<title>Eventname1</title>
<event id="5f76dc3808c8677ca3515213db89291ecaca9b2dbf3e6">
<start>00:00</start>
<duration>16:00</duration>
</event>
</room>
</day>

But the second event doesn't show up.

---

I've found out that an event that starts before 06:00 is not recognized and doesn't show up. For example:

<day date="2019-11-15">
<room name="ABC">
<title>Eventname1</title>
<event id="5f76dc3808c8677ca3515213db89291ecaca9b2dbf3e6">
<start>05:00</start>
<duration>04:00</duration>
</event>
</room>
</day>

doesn't work, but:

<day date="2019-11-15">
<room name="ABC">
<title>Eventname1</title>
<event id="5f76dc3808c8677ca3515213db89291ecaca9b2dbf3e6">
<start>06:00</start>
<duration>04:00</duration>
</event>
</room>
</day>

is working.

Why is that? Any suggestions about this issue?

Thank you so much!

[Wilm0r]

Sorry, yes this is definitely unusual. :( Apologies for the late response here, no clue whether you're still paying attn to this..

The reason the 05:00 start event is not even showing up is related to the day_change property, which in Giggity defaults to 06:00 when not specified. This itself is a super useful feature of course when a conf has events that last until or start after midnight.

Having events go past the day change would be more difficult to write support for. Giggity would have to internally split them, and possibly also specialcase them in the block schedule layout to prevent them from taking up a lot of otherwise blank space. One could as well split them in the source file, then, which I believe most events do.

Have you run into this issue again?