-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add slider style from yugecin/opsu-dance #263
Conversation
Thanks so much! 🎉 🎉 🎉 I might not get a chance to really test this for a few days, but my observations so far:
Also, what are "merged sliders"? I couldn't notice any difference with them on/off. |
|
Ooh, this looks nice. There's a bug for concurrent sliders on 2B maps (e.g. Lanturn's Endless Tewi-ma Park) with "Merge Sliders" enabled. With "Shrink Sliders" enabled, only the latest slider that started appears. The tracks of any sliders that started earlier and are still running disappear. From the 2B difficulty (middle started first, top started last): Example:
t=0: S1 starts With "Shrink Sliders" disabled, all concurrent sliders disappear when the shortest one ends, and they'll flash when they end. Example:
t=0: S1 starts Spinners don't seem to affect slider behaviour. Everything works as expected with "Merge Sliders" off. |
Yep I knew that that is possible, when a slider starts while an other slider is still going, the previous slider disappears when the merge & shrink settings are enabled. I couldn't find a map that had this issue so I left it like that, but I didn't think of the 2B maps... |
…er sliders is done earlier (2b maps etc)
Should be fixed :) |
Indeed it is. Thanks! The option hints can be a bit more descriptive. Maybe something like this:
For consistency with "Snaking sliders", perhaps they should also be renamed "Merging sliders" and "Shrinking sliders". |
src/itdelatrisu/opsu/Utils.java
Outdated
@@ -756,4 +756,14 @@ public static long getUsedMemory() { | |||
Runtime r = Runtime.getRuntime(); | |||
return r.totalMemory() - r.freeMemory(); | |||
} | |||
|
|||
public static class Pair<F, S> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eh... not a fan of this abstraction. It's barely more clear than just adding 2 elements in a row to your lists since this still doesn't tell you what they are, plus it's extra overhead.
Fair point, got rid of the Pair stuff. |
Signed-off-by: Jeffrey Han <itdelatrisu@gmail.com>
Didn't know how to name them, so I added it as 'Experimental slider style'