-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release v2.13 #1589
Release v2.13 #1589
Conversation
…91 chars This prevents missing \n at the end of long lines leading to a corrupted file. The long lines are still truncated when being read. Fixes #1439
… non-Windows SWELL skips line that do not contain =.
There is no need to make a copy of the string with all \n replaced by \0 when the original string can already have the \0.
The list was always scrolled to the top after clearing & rebuilding the entire list (+ an extra redraw causing flickering). Fixes #1456
selection to dynamic commands. Default number of slots is 16, max slots is SNM_MAX_DYN_ACTIONS. Using these actions will mark the project as dirty. Fixes: #1405
This commits makes AWClrTimeSelClkToggle construct a single instance of the ConfigVar (and also simplifies the condition).
…on click in ruler" settings Fixes #1442
Booleans are always true if they aren't false.
… if already contained in new filename/takename
…is a chapter marker (REAPER v6.19+)
…in NF_UpdateSWSMarkerRegionSubWindow description
…ash if MIDI octave display offset is set to a negative value https://forum.cockos.com/showpost.php?p=2421440&postcount=2918
This comment has been minimized.
This comment has been minimized.
This is weird, I set name of a new track so SWS v2.12 auto colors it, then script optionally gets that track color, darkens the color and sets the track color, but with v2.13 instead of the track color getting darker it changes to a black color. If I force my script to wait a bit (using defer loop) then the track darkening works as it does in current SWS release. Very weird! TESTED on: Win10_x64, REAPER 6.41 & v6.43_RC4 example, function DarkenColor(trk_colr) -- simple color darkener track = reaper.GetTrack(0,0) -- SWS auto colors the track when named. -- Optionally make the track a slightly darker |
Guessing the problem is, if you try to get the color of a track right after SWS has auto colored it , 2.13 now returns the wrong value? |
* AC_AUDIOIN (audio-input): track has an assigned audio input * AC_MIDIOUT (midi-output): track has an assigned hardware MIDI output
This allows for generalized scripts that take "arguments" by creating a cycle action that first uses this new ReaConsole command to prime a value in REAPER's non-persisted state, and then calling a custom script that subsequently reads the value.
…startup-action-functions' into v2.13
Broke since AppVeyor's September 2021 Ubuntu 18.04 image update
0065b61491a5580e3ee48b4c66d64c82176fe228 is required for enabling C++17, and also gets rid of all warnings about the register keyboard being deprecated.
Auto-color was indeed changed to be asynchronous (triggering on the next defer tick). This was done for performance reasons for the new track I/O and instrument FX filters and was applied to all filters for consistency. I've replaced that with a different solution (downside is it's unclear if it cover all cases, relies on REAPER sending redundant control surface notifications in a particular order). |
71e6bf1
to
5459fac
Compare
This comment has been minimized.
This comment has been minimized.
I've updated the release date to tomorrow. |
✅ Build sws 691-master completed (commit d1310bfde7 by @cfillion) Windows 64-bitWindows 32-bitmacOS x86 64-bitmacOS x86 32-bitmacOS ARM 64-bitLinux x86 64-bitLinux x86 32-bitLinux ARM 64-bitLinux ARM 32-bit |
Just a (maybe silly) idea...how about following the Reaper release tradition and letting users announce new SWS releases in the forum (the last ones you announced iirc). |
I suppose the majority of users with pre-release notifications enabled aren't necessarily active on the forum anyway... |
This merges all pull requests that were ready for a new pre-release. Not included are the drafts (#1449, #1467, #1493, #1514), incomplete (#1291, #1444) and unreviewed PRs (#1301, #1562).
If there's nothing to add/changelog typos/other changes to make, all that's left is amending the last commit with the correct release date in the whatsnew then merging the branch into master.
git submodule update --init
)