I've been a little quiet about the 2.0 release schedule. It is for purely personal reasons - I needed to get to grips with beaming in LilyPond, and so I have put the results of this work into the release. You can now set up the beaming rule you want by doing an example by hand selecting it, and invoking a command. And just when I thought this was done, I realised that the case I had needed manual beaming, so I needed to find all the places where it was needed. So I've coded up a Search & Replace command, something long in the back of my mind, but needing a real life use-case. How it works is that you make a selection and invoke Navigation->Seek->Search Rhythmic Pattern (or Ctrl-f, Ctrl-f) and this searches for the same sequence of note-durations on the staff. When found you can stop to edit, or if you have the edit commands recorded in the Scheme window you can execute them and continue.
Now, I *really* think it is time we moved to a release! Is a set of binaries possible now? Richard On Fri, 2015-08-28 at 19:10 +0100, Richard Shann wrote: > I've tested > > http://denemo.org/~jjbenham/gub/uploads/denemo-mingw-0.0.0.zip > > which is a getting close to the final 2.0 version. Can other windows > users please test. > > Richard > > > On Thu, 2015-08-27 at 13:13 -0500, Jeremiah Benham wrote: > > I have built a new mingw binary. > > > > Jeremiah > > > > On Aug 26, 2015 4:00 AM, "Richard Shann" <[email protected]> > > wrote: > > I've now added Score, Movement, Staff and Voice property > > editors to the > > Object editor, so that there is a consistent interface to > > editing things > > that have been added to a score. The Staff Property Editor > > gives access > > to directives added to time and keysignatures so that all > > Denemo > > Directives now have a user-friendly interface for editing them > > (provided > > the command creating them self-edits). > > > > I've updated the manual to reflect these additions - I think > > they > > constitute quite a change to Denemo use beyond the stage of > > entering > > music - previously when a property was added to, say, a key > > signature it > > was not easy to find out which command had been invoked. Now > > you can get > > up the editor and find out and, reverse or modify the effect > > if desired. > > There are still commands that do not self-edit but once I have > > been > > through fixing those I think the result will merit a change in > > the major > > version number - I propose this next version be version 2.0 > > > > Any feedback on the new properties editors would be most > > welcome (a new > > mingw binary would be helpful too for those poor souls still > > sticking > > with windows). > > > > Richard > > > > > > > > _______________________________________________ > > Denemo-devel mailing list > > [email protected] > > https://lists.gnu.org/mailman/listinfo/denemo-devel > > > > _______________________________________________ > Denemo-devel mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/denemo-devel _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
