Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Fix for #111
Fix for #108
Pretty straightforward I think? I think this covers the only two ways to exit the timer: inspection expiry and standard finish.
Added "Use scramble" feature for #97
I'm not really familiar with common Android architecture (intents/broadcasts/etc) but this seemed a rather neat way to do it. Feedback welcome.
Fix for #97
The history setting was being stored in an instance variable when changed, but not persisted back to the fragment arguments that are used when fragment is recreated (as happens in a rotation).
These were all suggested by build failures and warnings.
This is more consistent with standard presentation of settings. There's no need to call out the default value explicitly here – the default button in the dialog reveals it if needed. Instead, show the current value of the setting.
These are generated files, but I'm not sure how they are generated and wanted to ensure the build didn't crash in the meantime. Opened #112 to better document.
This adds a new menu item to the overflow button on the time dialog (from clicking on a solve in history) that switches to the main timer with that solve's scramble loaded.