Re: [Denemo-devel] Titles, buttons etc.

2016-02-17 Thread Haris Brkovic
Hello everyone. Sorry for delay. First problem with titles, movements etc. existed with my old files. I can't reproduce it again. It happened when first movement was open without notes then i opened second movement and numbers didnt appear. If it happen again and i manage to reproduce error I'l

Re: [Denemo-devel] Titles, buttons etc.

2016-02-15 Thread Phil (list)
On Mon, 2016-02-15 at 09:29 +, Richard Shann wrote: > > 2. Popup windows appear in the back of main window here in mac. For > > example when command center is open and popup windows is telling > > shortcut is already taken, it appears behind command center. It > > also happened in every version

Re: [Denemo-devel] Titles, buttons etc.

2016-02-15 Thread Richard Shann
On Mon, 2016-02-15 at 00:01 +0100, Haris Brkovic wrote: > Dear Richard, didn't write for a few days. Actually I was busy working with > Denemo. I'm trying to make as more costumization as possible to make my > typing faster and efficient. This kind of costumization which Denemo gives is > incred

Re: [Denemo-devel] Titles, buttons etc.

2016-02-15 Thread Richard Shann
On Mon, 2016-02-15 at 00:04 +0100, Haris Brkovic wrote: > So to finish mail which I accidentaly sent, I hope Denemo development is > still progressing in high speed as before. Well, it is indeed, but due to the nature of the work, it is not visible yet in the source repository. I've been working

Re: [Denemo-devel] Titles, buttons etc.

2016-02-14 Thread Haris Brkovic
So to finish mail which I accidentaly sent, I hope Denemo development is still progressing in high speed as before. Sincerely, Haris Poslano s mojeg iPhonea 15.02.2016., u 00:01, Haris Brkovic napisao: > Dear Richard, didn't write for a few days. Actually I was busy working with > Denemo. I'm

[Denemo-devel] Titles, buttons etc.

2016-02-14 Thread Haris Brkovic
Dear Richard, didn't write for a few days. Actually I was busy working with Denemo. I'm trying to make as more costumization as possible to make my typing faster and efficient. This kind of costumization which Denemo gives is incredible. Anyway, I want to report teo bugs in 2.0.3. 1. Sometimes t

Re: [Denemo-devel] Titles

2013-02-14 Thread Richard Shann
On Thu, 2013-02-14 at 14:11 +0100, Andreas Schneider wrote: > Hi, > > there seems to be a newly introduced bug with the titles. Titles (Simple > Titling) are small and left-aligned, which probably originates from the > \markup code put there. The produced Lilypond code seems messy. For > example,

[Denemo-devel] Titles

2013-02-14 Thread Andreas Schneider
Hi, there seems to be a newly introduced bug with the titles. Titles (Simple Titling) are small and left-aligned, which probably originates from the \markup code put there. The produced Lilypond code seems messy. For example, create a new score, set Score > Simple Titling > Title and Score > Simpl

Re: [Denemo-devel] Titles

2013-02-03 Thread Andreas Schneider
Am 03.02.2013 17:38, schrieb Richard Shann: > [...] It has the horrid consequence that if someone inserts a movement > before the one with the title for the score then that title= field is in > the \header{} block of the wrong movement. Similar things happen on swapping movements and Add movement

Re: [Denemo-devel] Titles

2013-02-03 Thread Richard Shann
On Sun, 2013-02-03 at 11:34 +0100, Andreas Schneider wrote: > When I have a piece with score titles and insert a movement before, the > score titles are present in the (now) second movement. On changing the > titles, those of the first movement are set, but those of the second > movement remain and

Re: [Denemo-devel] Titles

2013-02-03 Thread Richard Shann
On Sun, 2013-02-03 at 15:01 +0100, Federico Bruni wrote: > Il 03/02/2013 12:23, Richard Shann ha scritto: > > Simple Titles are done by fighting LilyPond - what Denemo calls the > > Title for the score is to LilyPond the title field in the first > > movement, and what Denemo calls the title for the

Re: [Denemo-devel] Titles

2013-02-03 Thread Federico Bruni
Il 03/02/2013 12:23, Richard Shann ha scritto: Simple Titles are done by fighting LilyPond - what Denemo calls the Title for the score is to LilyPond the title field in the first movement, and what Denemo calls the title for the movement is the subtitle field (and then a variable called print-all

Re: [Denemo-devel] Titles

2013-02-03 Thread Richard Shann
On Sun, 2013-02-03 at 11:34 +0100, Andreas Schneider wrote: > When I have a piece with score titles Is this using "Simple Titles" or "Book Titles" > and insert a movement before, the > score titles are present in the (now) second movement. On changing the > titles, those of the first movement are

Re: [Denemo-devel] Titles

2013-02-03 Thread Richard Shann
On Sun, 2013-02-03 at 11:34 +0100, Andreas Schneider wrote: > cannot be deleted (i.e. right-click > delete > directive does not work). I just tested this: New score Create Score->Simple Titles->Title Insert Movement Before Go to second movement Right click on the title button (Gives the "Adva

[Denemo-devel] Titles

2013-02-03 Thread Andreas Schneider
When I have a piece with score titles and insert a movement before, the score titles are present in the (now) second movement. On changing the titles, those of the first movement are set, but those of the second movement remain and cannot be deleted (i.e. right-click > delete directive does not wor

Re: [Denemo-devel] titles

2012-11-02 Thread Richard Shann
On Wed, 2012-10-31 at 11:07 +0100, Andreas Schneider wrote: > copyright (Score > Titles > Simple Titling > Copyright) and tagline > (Score > Titles > tagline) do not work. The created Lilypond code has > escaped quotation marks. These also appear in the tagline (or copyright) > itself and can't be

[Denemo-devel] titles

2012-10-31 Thread Andreas Schneider
copyright (Score > Titles > Simple Titling > Copyright) and tagline (Score > Titles > tagline) do not work. The created Lilypond code has escaped quotation marks. These also appear in the tagline (or copyright) itself and can't be deleted. I have removed my .denemo-0.9.7 directory to make sure that