Gig-o-Matic / GO3

GNU General Public License v3.0
10 stars 8 forks source link

Gigs without specified time are archived too early #554

Open mmendelson222 opened 1 month ago

mmendelson222 commented 1 month ago

If a time is not specified, the gig disappears from the schedule at 12AM, and can only be found on the "Archived" list.

This occurs from time to time with our band, because rehearsals "are at the usual time".

One fix would be to archive the gig AT THE END of the day it is scheduled.

Another fix I suppose could be to REQUIRE a start time when creating a gig.

Thanks!

For purposes of archiving, the gig is considered "yesterday" (see rehearsal at bottom of list): Screenshot 2024-10-05 at 11 17 32 AM

Gig summary indicates that it is today. Screenshot 2024-10-05 at 11 17 54 AM

aaronoppenheimer commented 1 month ago

Hi Michael - someone else pointed this out just today. I have a fix and will roll it out shortly.

On Sat, Oct 5, 2024, at 11:26 AM, Michael Mendelson wrote:

If a time is not specified, the gig disappears from the schedule at 12AM, and can only be found on the "Archived" list.

This occurs from time to time with our band, because rehearsals "are at the usual time".

One fix would be to archive the gig AT THE END of the day it is scheduled.

Another fix I suppose could be to REQUIRE a start time when creating a gig.

Thanks!

Gig (rehearsal) is today, and already archived. Screenshot.2024-10-05.at.11.17.32.AM.png (view on web) https://github.com/user-attachments/assets/a66f9e8e-a979-4d38-b3f8-21162bb0d461

Gig summary indicates that it is today. Screenshot.2024-10-05.at.11.17.54.AM.png (view on web) https://github.com/user-attachments/assets/f3641ec4-d85e-4fa4-9ca6-ecf866994da3

— Reply to this email directly, view it on GitHub https://github.com/Gig-o-Matic/GO3/issues/554, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWDDNUZT6WSRNPS7WQPMV3Z2AAIZAVCNFSM6AAAAABPNN3OK2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DQMJYGI2DANI. You are receiving this because you are subscribed to this thread.Message ID: @.***>