Holger Stenger
Holger Stenger
While researching a fix for #101 I noticed several APIs were deprecated in Stash 3.0 and will be removed in Stash 4.0. The affected APIs include [SshUrlCloneResolver](https://developer.atlassian.com/static/javadoc/stash/3.0.0/ssh/reference/com/atlassian/stash/ssh/api/SshCloneUrlResolver.html) and [NavBuilder.Repo.clone()](https://developer.atlassian.com/static/javadoc/stash/3.0.0/api/reference/com/atlassian/stash/nav/NavBuilder.Repo.html#clone%28java.lang.String%29). The...
## Description The REPL outputs string literals containing the escape sequence `\&` but this escape sequence is not accepted as input. ## To Reproduce In the REPL: ``` > "\x0000001"...
The "Manual BPM Calculation" window does not react to track changes at all. In particular it still shows the last BPM value. There should be an option to automatically reset...
The BPM value for a track should be reset if the results of the automatic analysis are ambiguous. Ambiguouity should be detected based on the number or range of candidate...
The automatic analysis results window shows only the selected candidate BPM value. There is no indication about the confidence level or whether the BPM varied throughout the track. The results...
It should be possible to start a manual BPM analysis from th results window of the automatic analysis. Suggested by [g-stankovic](http://www.hydrogenaud.io/forums/index.php?s=&showtopic=77142&view=findpost&p=868557).
The command opens a window which applies to the currently playing track, no matter which track was selected. The window also does not indicate which track will be modified. See...
The "Manual BPM Calculation" window should contain buttons to halve and double the calculated BPM value like the automatic analysis results window. Suggested by [Z4g5r](http://www.hydrogenaud.io/forums/index.php?s=&showtopic=77142&view=findpost&p=868456a).
The "Automatically analyse BPMs" command asks for confirmation when all tracks already have a BPM tag. The user should be able to disable this confirmation via a configuration option. Suggested...
The "Manual BPM Calculation" window should be closed after the user clicks the "Update files" button and the file was successfully updated. This behaviour should be controlled by a configuration...