Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event durations are always assumed to be 15 minutes. #4

Open
ZDBioHazard opened this issue May 1, 2014 · 1 comment
Open

Event durations are always assumed to be 15 minutes. #4

ZDBioHazard opened this issue May 1, 2014 · 1 comment

Comments

@ZDBioHazard
Copy link
Owner

The way I have the event list set up, the system can't tell how long events last, or when events overlap. This is not usually a problem, but a few events, such as Claw of Jormag often run longer than the 15-minute window this app assumes.

I have a plan to fix this, just need some time to design a new event database format.

I would like to ask for assistance finding average pre-event and main-event duration times, as the current schedule does not allow me to visit a lot of these events very often.

@ZDBioHazard
Copy link
Owner Author

Oh, forgot to mention displaying multiple events at one time was fixed ages ago in c730c87.

All events still default to 15 minutes long though. I have more accurate durations in-progress in a local branch, but I still need to collect more accurate time data.

@ZDBioHazard ZDBioHazard changed the title Only one event can be active at one time Event durations are always assumed to be 15 minutes. Oct 9, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant