denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Denemo-devel] another stupid question


From: Richard Shann
Subject: Re: [Denemo-devel] another stupid question
Date: Thu, 03 Oct 2013 17:08:52 +0100

On Thu, 2013-10-03 at 09:39 -0400, Bric wrote:
> 
> > On October 3, 2013 at 9:02 AM Bric <address@hidden> wrote:
> > 
> > 
> > 
> > 
> > > On October 3, 2013 at 7:01 AM Richard Shann <address@hidden> wrote:
> > > 
> > > 
> > > On Thu, 2013-10-03 at 10:29 +0100, Richard Shann wrote:
> > > > I'll turn that into a command when I get a moment
> > > 
> > > I have done this, in git now. I noticed that there is already a command
> > > there to play the note or chord at the cursor from the current staff,
> > > using a different route altogether. 
> > > 
> > > Also, there is a bug: when you set the end play position if the cursor
> > > is on the first note in the bar it sets the end play after that note,
> > > not before. The script (DenemoSetPlaybackEnd) in actions/denemo.scm
> > > needs fixing.
> > > 
> > 
> > 
> > that's great.  But here's yet another stupid question:  If I updated and
> > recompiled my git tree, and then installed it in the same location as 
> > previous
> > install, would that clobber my current shortcuts and user settings? 
> > 
> > Any docs on backing up one's custom settings?
> > 
> 
> To answer my own stupid question:  my shortcuts seem to be preserved, across
> recompiles/re-installs.

Yes, they become somewhat "hidden" when we move to a new version number.
They in ~/.denemo-1.0.n/actions/Default.shortcuts where 1.0.n is the
current version. There is no real knowledge or documentation about
copying over an old shortcuts file to a new version. 
What you may find though is that new commands are not present: you would
have to use the right-click->More Commands menu item (or More menu and
descend the menus) to get the new commands, since once you have created
shortcuts you also have your own commands file which won't get updated.
I think you could set ~/.denemo-nnn/actions/Default.commands to be a
link to the system one (e.g. /usr/share/denemo/actions/Default.commands
or wherever it is installed) and then you will get all new commands on
re-installing Denemo from git build.

> 
> Sorry, i was being extra-cautious — I would cry over the wasted time if I lost
> what I had amassed the last three weeks.
> 
> _______________
> 
> Back to the feature:  OK! It works for me. We're getting there!  This is
> awesome. (I assigned "Ctrl+p" for myself)
> 
> Now if only we could have full vertical ?  PLay the vertical stack of notes
> across all staffs, at the cursor?

As I mentioned something like that is already there, I put the new
command just after it.

> 
> I'm not asking for the full monty just yet — which would be computing the most
> RECENT note, with respect to the cursor, and including it in the set of
> audibles. In other words, check if durations of preceding notes extend beyond,
> across the cursor, even if the notes are not written exactly at the cursor 
> (but
> their duration might extend through that point in time) (Maybe THAT would be
> phase two?)
> 
> For phase one, if we could just get the audible stack of all notes *AT* the
> cursor (across all (unmuted) staffs)?
> 
> And then, of course, some easy progression control with the arrows, perhaps?
> (That would just require the additional directive to progress forward, and
have you played with the Mouse Conductor?
> prompt for the next incremental, vertical playback)

All that sounds quite scriptable - you may need to start working on some
scheme scripts to get it to happen though :)

Richard






reply via email to

[Prev in Thread] Current Thread [Next in Thread]