groundhog | Grasshopper plugin , a set of reference models | Topic Modeling library

You've surpassed the limits of your chosen numeric representation.

This might be surprising since most of the time, when mixing numeric types, C++ will convert to the type that can best represent the result. For example, adding an int and long long is calculated as a long long. Adding a float and double is calculated as a double. However, you've chosen one of the odd routes by adding an integer type and a float.

By the usual arithmetic conversions, adding any integer type and a float is calculated as a float. Any integer type. If you happen to have a 128-bit long long and a 32-bit float, adding them produces a 32-bit float. The float is treated as if it can better represent numbers, which has merit. A typical 32-bit float does have about the same range as a 128-bit integer, with the benefit of being able to represent non-integers. However, while this thinking might be behind the rule, the rule is simply that a float combined with an integer type produces a float.

Apply this to the line that updates totalSeconds.

I think that a better and more logical approach would be to store the event, rather than dates, and then every event has a corresponding date. When the user taps on the day, you fetch all the events that have the date property equal to that date.

An array is the most light-weight data structure you can use and most appropriate if the number of elements does not change. The only issue is that you must declare the reference type of the array to all be equal. I would suggest all the classes extend from a parent class, say 'Animal'. In the solution below, I have extended all the classes from Animal: