Weird behaviour of timing points in the editor

[snalgae]

Type

Game behaviour

Bug description

Just messing around in the editor. I think the fact that the compose tab went blank when I pressed undo once made me notice this. After some tinkering I actually discovered that there is weirdness related to timing points: Bugs:

• [ ] Cloning a timing point, removing the timing attribute, enabling an effect attribute and enabling kiai time, and then undoing makes a timing point without the yellow tick on the timeline, fixed after saving and reloading the beatmap
• [x] Undoing a timing point while in a compose tab deloads the compose tab (https://github.com/ppy/osu/pull/28776) and the yellow tick also disappears on an affected timing point.
• [ ] Making a timing point using "+ Add at current time" when there's already another timing point, does not automatically update the bars. When you place it, it appears without the white thick bar lines and the timeline still uses the bars from the previous timing point (you need to wiggle the timeline or change attribute settings to make it update).
• [ ] Skip bar line does not visually change the white bars, while the metronome sounds are affected as intended.

Unintuitive stuff:

• [ ] The set up of attributes (enabling timing or effect) does not save them. So pressing ctrl+z skips the enabling of the attribute and affects an action before it. It also affects doing something inside of an attribute and then undoing back to the starting state of an attribute (like when you want to revert back to the original state for timing) . In that case it disables the attribute and can remove the timing point itself.
• [ ] I was confused about the scrolling of the waveforms inside of the timing attribute because I thought the scrolling was vertical, but it actually scrolls horizontally.

I can make a video/screenshot of a specific issue on request if you need more information. I made one video for the second bug before discovering more issues.

Screenshots or videos

https://github.com/ppy/osu/assets/104220939/41f6e689-da4e-4eb2-a1c5-bdc7049456d8

Version

2024.625.2

Logs

compressed-logs.zip

[snalgae]

Also I think clicking the specfic lazer version in the menu settings should copy the version to the clipboard instead of bringing to the changelog.

[bdach]

Also I think clicking the specfic lazer version in the menu settings should copy the version to the clipboard instead of bringing to the changelog.

That is irrelevant to the rest of this issue and also makes no sense to my (why would you want that?)

[snalgae]

Also I think clicking the specfic lazer version in the menu settings should copy the version to the clipboard instead of bringing to the changelog.

That is irrelevant to the rest of this issue and also makes no sense to my (why would you want that?)

I mean why would anyone click on the version number itself? It feels redundant to open the changelog via the version number, when there is a tab for it. I just disliked typing in the version of the lazer manually, but maybe clicking on it to get it is excessive.

[frenzibyte]

Check again, it doesn't just open the changelog, it opens the specific entry of the currently running version of lazer. Either way, if you feel strongly about this, open a separate issue thread.

[snalgae]

I do not feel strongly about this and I apologize for the inconvenience.

Edit: This weird thread (messages about this) should be hidden or deleted because it's pretty unrelated and clogs up this space.