Best Of

Yes - please add this.

@RobWilk — I hope you are right and that it is something simple.

We are, of course, assuming that it is the new register that is the problem. That seems pretty likely, but I don't know what else is part of the Early Access program.

Unfortunately, it doesn't seem like v.4.80 was fully tested against whatever is included in Early Access. Maybe they will do that now.

@DryHeat They're still developing the new register, and something real simple could be causing it to fail right now — They probably made some code changes recently, and made a slight error which caused an exception to make it 'crash'. For example, an app I wrote recently ran into a crash when something the user did unexpectedly caused a for loop to count down rather than count up (instead of a for loop counting from 1 to 5 for example, it tried to count from 1 to 0 which is in the wrong direction for a loop which normally counts up, a quick range check fixed that in minutes).

Once the register is 'complete' they probably won't touch the working code too often, so it 'should' not break often outside of early access.

-Rob

EDIT: p.s. in the case of my app, i had previously checked that the number of students was > 0, but what the user did unexpectedly (my sister being the user) was mark every single student absent, then tried generating random groups 'excluding absent students'. My fix was to verify that the appropriate number (in this case, # of present students when absent excluded) was checked.