NoteWorthy Composer Forum

Forums => General Discussion => Topic started by: Rick G. on 2007-01-24 11:56 am

Title: Why not support: |Text:, |Font:, |Wide: and |Pos: for more Objects?
Post by: Rick G. on 2007-01-24 11:56 am
I count 19 objects used by NWC2 as of Beta 2.13:
Code: [Select · Download]
!NoteWorthyComposerClip(2.0,Single)
|Note
|Rest
|Chord|Pos:,
|RestChord|Pos2:
|Bar
|Clef|Type:Bass
|Dynamic|Style:p
|TempoVariance|Style:Fermata
|Flow|Style:Fine
|TimeSig|Signature:4/4
|Instrument
|Key
|MPC|Controller:tempo|Pt1:0,0
|PerformanceStyle|Style:Solo
|Ending|Endings:1
|Tempo|Tempo:
|SustainPedal
|Text|Text:"X"
|DynamicVariance|Style:Crescendo
!NoteWorthyComposerClip-End
Every one of them uses some text except a barline without a repeat.
|Text:, |Font:, |Wide: and |Pos: has no effect on most of them. I'd like to see that change.
I'm not asking for the user interface to be changed in any way, but ...

If the paste parsing routine would allow it, the program could gain much power and flexibility:


And finally, Ending:
They are seldom in the right place. Pos: would fix that. Another use:
|Ending|Endings:2|Text:"to next strain."|Font:StaffItalic
When I give music done in NWC to others, the most common question is:
What is this D. in the second ending? I'd rather not be asked.

I'm sure that other users would invent other uses. In time, some of these would make it into the User Interface. Some might cause problems. these could be resolved or filtered out over time. For the casual user, none of this would make NWC2 more complicated.
Title: Re: Why not support: |Text:, |Font:, |Wide: and |Pos: for more Objects?
Post by: David Palmquist on 2007-01-24 02:20 pm
Interesting ideas.  How many of them would be solved by having two choices for Staff Metrics? 

In other words, you;'d have the default, but could highlight a certain range of staff elements, choose Properties, and select a second font for staff metric in the highted range only.

Title: Re: Why not support: |Text:, |Font:, |Wide: and |Pos: for more Objects?
Post by: Lawrie Pardy on 2007-01-25 09:57 am
G'day Rick,
I find some interesting ideas here...

I shall need to contemplate some of them but off the top of me head I think there is much merit in your suggestions.

While many of the issues you suggested can be worked around using text entries it would be much more satisfying to have it built in.
Title: Re: Why not support: |Text:, |Font:, |Wide: and |Pos: for more Objects?
Post by: Rick G. on 2007-01-25 12:54 pm
How many of them would be solved by having two choices for Staff Metrics?
With no control over the string displayed, nothing could be horizontally positioned "on the fly".
You would gain noteheads, but no flag or width control.
Clef, Key and TimeSig might be made to work.
TempoVariance could do marcato or staccatissimo, but not both with the same font.
Endings wouldn't benefit at all.

Your plan would leave users to the mercy of font designers, mine would open new vistas to anyone who could cut, paste and use NotePad.

Thanks to both of you for responding. This idea may be too radical for Beta.  I regret not becoming active in the program earlier.