- Add Restart MIDI Input command to allow restarting MIDI input when changing devices
- Merge MIDI input bugfixes by paradox460
- Unbump
jzz
dependencies updated in 1.7.0 due to virus scan blocks
- Update dependencies
- Renew VSCE PAT token and retry releasing as 1.7.0 did not release successfully
- Fix #341
- Thanks paradox460
- Update dependencies
- Fix #253
- Kill the previous compilation job and let the next one take over
- Fix #252
- Add a
Compiling...
status bar icon as well as a Compilation Failed one to signify status.
- Add a
- Fail more predictably on MIDI input and output
- For input, fail when no input devices are found
- For output, show the status bar items more leniently (all LilyPond files)
- Fail when MIDI file not found with a more descriptive message.
- Update dependencies
- Fix an issue with remote servers/dev containers crashing due to the absence of sound devices in a Linux based container
- Update documentation
- Output
lilypond
compilation stdout and stderr to theVSLilyPond: Compilation
output channel.
- Update documentation
- Use LilyPond PDF Preview extension which supports Point-and-Click.
- Update documentation
- Update dependencies
- Update documentation
- Use LilyPond Syntax extension which supports Scheme syntax for syntax highlighting
- Update dependencies
- Add StatusBarItem showing loaded LilyPond version
- Update dependencies
- Temporarily remove
jeandeaual.lilypond-syntax
as it causes VSLilyPond to not be able to start up.
- Take extension out of preview
- Fix typos in README
- Use LilyPond Syntax extension which supports Scheme syntax for syntax highlighting
- Update dependencies
- Update dependencies
- Refactor tests
- Update dependencies
- Fix #168: status bar was not working due to missed items when the extension namespace was changed.
- Update dependencies
- Add formatter
- Update dependencies
- Change namespace of extension commands to prevent clashing.
- Minify images
- Bumped dependency versions
- Update icon
- ❗ Deprecated redundant commands, see COMMANDS.md.
- Fix bug in which warnings/errors in included files erroneously show in current file
- Include warnings from lilypond
- Enable settings to up to folder level
- Add feature to allow main file compilation
- Add icon
- Add configuration to let users set path to lilypond executable.
- Fix #36
- Check for midi files by following the sequence:
.midi
,.mid
,audio.midi
- Check for midi files by following the sequence:
- Update dependencies
- Kill timeout for LilyPond spawns - might expose this as user configurable in the future
- Add note in README.md about active development
- Move extension back to preview mode
- Add warning to Catalina
- Make explicit minimum VSCode version
- Fallback storagePath to globalStoragePath for IntelliSense
- Add extension installation instructions
- Correct typo in documentation
- Added dependency for LilyPond AutoComplete (Commands & Keywords)
- Optimise process spawning by limiting one each for compilation and intellisense
- Code optimisations
- Using output channels for failing processes to notify user
- Added
Play from...
option for MIDI playback, allows user to input timestamp for MIDI to start from - Only show status bar items for MIDI playback & input when options are valid
- Fix MIDI Input accepting messages that are not MIDI music messages (e.g. Modulation)
- Update documentation
- Add setup guide
- Refactored code base
- Added test suite
- Fix extension pointing to wrong build directory, causing it being unable to start up in some cases
- Add truefire's VSCode extension as dependency
- Update documentation and GIFs
- Fix #5, revert to non-webpack version.
- Remove unneeded files
- Minor package.json changes
- Clean up development items
- Use webpack to optimise extension
- Initial release