FWIW, there is an open issue that I think also relates to this in some way:
https://musescore.org/en/node/54691.  Maybe it's only related in my head
:-).  But I think they perhaps both have to do with not having enough
context at the point where it is needed.

On Sat, May 2, 2015 at 4:34 AM, Lasconic <lasco...@gmail.com> wrote:

> Off the top of my head, I would check Measure::findAccidental()
>
> lasconic
>
> 2015-05-02 10:25 GMT+02:00 Jim Newton <jimka.i...@gmail.com>:
>
>> As some of you may know, I'm working on an enhancement to musescore which
>> implements ornament articulations such as trills (and others).  I'm making
>> heavy use of the function diatonicUpDown, which looks at a key and
>> calculates intervals restricted to the key signature.    This works great,
>> but is limited as mentioned in  this forum posting
>> <https://musescore.org/en/node/56281#comment-269526>  .
>>
>> In particular, I'd like to get a trill such as
>> <
>> https://musescore.org/sites/musescore.org/files/Screen%20Shot%202015-04-30%20at%2012.14.50.png
>> >
>> .
>>
>> Is there a similar function to diatonicUpDown which I can use which not
>> only
>> looks at the key, but also looks to see which notes are most recently
>> sharpened, flattened or natural-ed earlier in the measure?
>>
>> I notice that the interactive note entry in musescore understands
>> accidentals.  I.e., in the key of G, if I enter an F it is implicitly
>> interpreted as F#, but if is use the down arrow to make it F natural, then
>> enter another F, it is understood to be natural.
>>
>> Of course I could write code to examine the measure backward from the note
>> searching for such a note.  Making this function property look at all the
>> voices in the measure could be tricky. Maybe there is already such a
>> function, or at least an implementation I can look at and copy.
>>
>> I'd appreciate any clue about the correct way to code this.
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://dev-list.musescore.org/ISO-version-of-diatonicUpDown-which-understands-accidentals-tp7579271.html
>> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Mscore-developer mailing list
>> Mscore-developer@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>>
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Mscore-developer mailing list
> Mscore-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
>


-- 
Marc Sabatella
m...@outsideshore.com
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Mscore-developer mailing list
Mscore-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Reply via email to