Re: [Denemo-devel] Context Error

[alex stone]

Ok, i'll try that.

On Mon, Dec 14, 2009 at 9:30 PM, Richard Shann <address@hidden> wrote:
> I know why this has started happening. You will need to set the lilypond
> version field score properties->paper->lilypond version to a value such
> as 2.8.8 which will tell it you have old syntax in there.
>
> It used to be set always, and now it isn't as Denemo will always
> generate current LilyPond, although some scripts may not. They should
> declare their lilypond number etc, but they don't yet.
>
> I think we could probably upgrade the instrument name scripts to use
> newer syntax as my out of the box Debian uses the newer syntax, and
> Debian is always pretty out of date.
>
> Richard
>
>
> On Mon, 2009-12-14 at 21:20 +0300, alex stone wrote:
>> Interesting that i can kill the first instrument name (in my case
>> piccolo), leave the rest in, and it displays correctly now.
>>
>>
>>
>> On Mon, Dec 14, 2009 at 9:18 PM, alex stone <address@hidden> wrote:
>> > That did the trick.
>> > Thanks for the heads up.
>> >
>> > Alex.
>> >
>> > On Mon, Dec 14, 2009 at 9:17 PM, alex stone <address@hidden> wrote:
>> >> Ok, i'll try my version without instrument names, and see what happens.
>> >>
>> >>
>> >>
>> >> On Mon, Dec 14, 2009 at 8:48 PM, Richard Shann <address@hidden> wrote:
>> >>> Well, I can't see any errors,
>> >>> attached is a simple example, three staffs with the second and third
>> >>> making a staff group.
>> >>> The lilypond looks fine but it prints out wrongly. I guess there are a
>> >>> few more bits to chop out (the intrument name syntax changed at some
>> >>> point...)
>> >>> ah, yes, if I chop out the instrument names it is ok. Someone will have
>> >>> to investigate the instrument name syntax (perhaps it has to be
>> >>> differently placed...)
>> >>>
>> >>> Richard
>> >>>
>> >>>
>> >>> On Mon, 2009-12-14 at 20:20 +0300, alex stone wrote:
>> >>>> Ok, i've started a new test project and so far it works correctly, so
>> >>>> i guess it's not worth wasting anytime on the posted one.
>> >>>>
>> >>>> Sorry for the noise.
>> >>>>
>> >>>> Alex.
>> >>>>
>> >>>> On Mon, Dec 14, 2009 at 8:17 PM, alex stone <address@hidden> wrote:
>> >>>> > I've been through every staff to ensure there's no incomplete starts
>> >>>> > and ends, and the result is still the same.
>> >>>> > This is a recent phenomenon, and up until the last week (i think),
>> >>>> > this wasn't a problem.
>> >>>> >
>> >>>> > http://stashbox.org/735015/Context2.png
>> >>>> >
>> >>>> > Anyway, it's cropped up suddenly, and i'd be interested to know if
>> >>>> > other denemo users have this, or it's just my setup somewhere.
>> >>>> >
>> >>>> > Here's the denemo project used in this test, if it's any help.
>> >>>> >
>> >>>> > http://stashbox.org/735025/siberian%20tales%20notate1.denemo
>> >>>> >
>> >>>> > Alex.
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > On Mon, Dec 14, 2009 at 7:11 PM, Richard Shann <address@hidden> wrote:
>> >>>> >> On Mon, 2009-12-14 at 17:54 +0300, alex stone wrote:
>> >>>> >>> Moving on with testing, and the following appears when i try to set
>> >>>> >>> context for a project.
>> >>>> >>>
>> >>>> >>> Although this picture is of the 1st violins as Context Start, the 
>> >>>> >>> same
>> >>>> >>> happens for all context based directives, when applied from staff
>> >>>> >>> properties. (Piano, Choir, etc...)
>> >>>> >>>
>> >>>> >>> http://stashbox.org/734849/Context1.png
>> >>>> >>>
>> >>>> >>>
>> >>>> >> This is, I think, a context start without a context end. I'm guessing
>> >>>> >> this from the console message about a missing >> which would end the
>> >>>> >> context - these are LilyPond contexts set up by applying the context
>> >>>> >> start or end properties to the appropriate staffs from the
>> >>>> >> staffpropdialog. This is all old built-in stuff, there is no checking
>> >>>> >> for you, and nothing to show you if a staff is set as a context 
>> >>>> >> start or
>> >>>> >> context end. :-(
>> >>>> >> you have to step through the staffs looking at the props dialog to 
>> >>>> >> see
>> >>>> >> which contexts are set. (Unless you can read the LilyPond, where you 
>> >>>> >> can
>> >>>> >> see which one starts or stops wrongly).
>> >>>> >> Richard
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > --
>> >>>> > www.openoctave.org
>> >>>> >
>> >>>> > address@hidden
>> >>>> > address@hidden
>> >>>> >
>> >>>>
>> >>>>
>> >>>>
>> >>>
>> >>> _______________________________________________
>> >>> Denemo-devel mailing list
>> >>> address@hidden
>> >>> http://lists.gnu.org/mailman/listinfo/denemo-devel
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> www.openoctave.org
>> >>
>> >> address@hidden
>> >> address@hidden
>> >>
>> >
>> >
>> >
>> > --
>> > www.openoctave.org
>> >
>> > address@hidden
>> > address@hidden
>> >
>>
>>
>>
>
>
>
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/denemo-devel
>



-- 
www.openoctave.org

address@hidden
address@hidden