Skip to main content ↑ ↓
Recent Posts
4
General Discussion / Re: Avoid saving ActiveStaff, CaretIndex and CaretPos in nwctxt
Last post by Lawrie Pardy -
Hi Jonas,
These things also occur in the NWC file.  For completely different reasons sometimes I'm fine with it and sometimes it's an irritation.  I forget when this was introduced, and a quick look at the change information available on the main NWC site doesn't seem to say, but I'm sure it wasn't always like this.

I think I would like to see your proposal changed just slightly.  Rather than limit it to nwctxt files, make it so that there is an option whether or not to save these positional data at all.

If you want to add complexity, have 2 toggles: one for NWC files, and one for nwctxt files.

As a workaround maybe try to educate your other users to remember to move the cursor to the start of the top staff and press <0> (zero) before saving.  This will position the cursor at staff pos 0, current duration 1/4, standard notehead etc. at the start of the top staff.  If everyone can remember to do this then the positional data will always be the same.  Not a solution I know, and it depends on users being able to remember to do it...  Why do I feel like it'd be the same as trying to push a piece of string uphill?  :))
5
General Discussion / Avoid saving ActiveStaff, CaretIndex and CaretPos in nwctxt
Last post by jonashogstrom -
Is there any chance that the position of the cursor/caret in the editor could be excluded from the nwctxt file?

Background: In my choir we use git (distrbuted version control system, popularized by github among others) to store our digital music and pdfs. When multiple people fix errors in the nwc-files, we sometimes run into conflicts, because each user will (unknowingly) modify the line in the file that stores the position of the caret. Git is good at resolving simultaneous changes as long as they occur on different lines, but when two users edits the same line, there will be a merge conflict that needs to be resolved by hand.

I'm a developer by trade and resolving merge conflicts is part of my job description, but far from everyone in my choir is comfortable with 3 way diff tools... Avoiding unnecessary conflicts would reduce the number of times they need to ask me for help :)

/Jonas
7
General Discussion / Re: Including small note-heads in a NWC score
Last post by Mike Shawaluk -
Since that older thread was written, NWC has a new feature called user objects or plugins, which is a way to add new features to NWC for display and playback. One such plugin that was created is called CueHeads, which is a fairly easy way to add cue-sized notes to a score. You can read about it here.

Note: you don't need to install the object; if you have NWC 2.75 installed, it is already included.
9
General Discussion / Re: Scriptorium Update
Last post by Richard Woodroffe -
Folks
The Scriptorium has been updated with works submitted by :

Maurizio Spagni   La gazza ladra (ouverture) piano reduction    (Rossini)
Richard Woodroffe   Die Sommernacht (Version 2) D289   (Schubert)

https://nwc-scriptorium.org/whatsnew.html

If you would like to be notified every time the Scriptorium is updated, please send an e-mail  requesting Scriptorium Update    notification to nwcscriptorium "at" gmail "dot" com

Stay safe 

Richard