Lasconic wrote:
>> Yes, I used +, however, it doesn't quite work as expected. I expect the
>> following: 1 enter a note
>> 2 type + (nothing is visible, or maybe a message in the lower
>> border)
>> 3 change time duration, or add dot or whatever
>> 4 enter second note. Now the tie and the second note are shown and
>> the cursor is set to the next entry.
>
> It does not work like this. Read tie chapter again :
>
http://www.musescore.org/en/handbook/tieYes. I read that several times. Sorry I wasn't clear. Tieying over a
bar-line is OK, however, tieying e.g. a 1/8 note to a halve note in the
same measure doesn't work as expected.
>
>> I didn't know the Ctrl-F for goto. However, it always brings me to the first
>> system and doesn't show the cursor, only the first note (of the measure
>> number entered) is marked with blue (first layer). I don't know how to go to
>> e.g. the third system.
>
> Indeed for the moment
That's a pity
>
>> I encountered a few other 'quirks'.
>> In this new version when I enter a 8va marking, it works correctly. However,
>> when I want to extend the line it sometimes (but not always) becomes endless
>> and when I try to use the line inspector, it crashes.
>
> If you manage to have a logical sequence. Please post a bug report:
>
http://www.musescore.org/en/project/issues:That's the problem with intermittent errors. You don't know which
combination of instances produce the error.
>> Another small thing: how can I have measure numbers on all staffs?
>
> In the menu : Style->Edit Style-> Numbers
>
Yes. Of course I had found that. However, it doesn't work (it is ticked).
>
>> I also would like to know where the object inspector is explained. I used to
>> work with object Pascal ( a long time ago) where the same kind of tool was
>> available. However, that was directly linked with the code here I have no
>> idea.
> Nowhere but in the code :)
I don't have the code!
>
>> As I think this program is very important if I could contribute I would like
>> to try. I have programming experience (from my former life) with Fortran and
>> Pascal but NOT C ( in my former life we had C- and java programmers who did
>> the work!) and of course I don't know Qtscript but my experience is that
>> learning new languages is simply learning the rules. Programming - in an
>> object environment - is not so much different in different languages but I
>> may be completely wrong.
>> I made the switch from 'linear' thinking (as in Fortran and Pascal) to
>> 'object' thinking as in object Pascal and Delphi and C++ (but the latter I
>> have never used).
>
> The places to start :
http://www.musescore.org/en/development>
http://www.musescore.org/en/node/76I'll go and take a look.
>
> Lasconic
>
Thanks,
Joep
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship.
http://www.creativitycat.com
> _______________________________________________
> Mscore-developer mailing list
>
[hidden email]
>
https://lists.sourceforge.net/lists/listinfo/mscore-developer>
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship.
http://www.creativitycat.com
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
