|
| From: | Jeremiah Benham |
| Subject: | Re: [Denemo-devel] pdf Files out of sync on mac |
| Date: | Sat, 21 Dec 2013 11:58:37 -0600 |
On Dec 21, 2013 9:49 AM, "Richard Shann" <address@hidden> wrote:
>
> On Sat, 2013-12-21 at 09:41 -0600, Jeremiah Benham wrote:
> > Here is some more info....
> > I turned off window decorations and the problems were still there.
> > They were a bit worse because I could not kill the window to force the
> > refresh. I turned off continuous typesetting and then clicked on
> > refresh in the printview window but nothing appeared to happen. If
> > window decorations were on I could kill the window to force the
> > refresh. I monitored the date/time on the files in /tmp and both
> > the .ly and .pdf updated when I clicked refresh. Nothing updated in
> > evince. With window decoration off I had to hit refresh again. Then a
> > popup popped up (behind the evince window) asking me to kill the
> > current print job. I clicked yes. Then evince refreshes.
>
> This all sounds consistent with the child_watch never seeing the pid
> die. You could write a very crude work around that would keep checking
> for the print job finishing ... does the top or ps command show that the
> LilyPond process does actually finish and not go zombie or something?
>
Good call! I see the lilypond was running even after 30min. Once I killed lillypond evince refreshed. Why does lilypond exit correctly with export pdf but not printview refresh?
Jeremiah
> Richard
>
>
> >
> > Jeremiah
> >
> > On Dec 21, 2013 8:17 AM, "Jeremiah Benham"
> > <address@hidden> wrote:
> > On Fri, Dec 20, 2013 at 07:20:30PM +0000, Richard Shann wrote:
> > > Well, it seems that somehow the cycling between A and B is
> > getting out
> > > of step. You could try turning that off by not compiling in
> > these two
> > > lines (in print.c:78 and 79)
> > >
> > > get_print_status()->cycle = !get_print_status()->cycle;
> > > /*gint success =*/ g_unlink
> > (get_print_status()->printname_pdf[get_print_status()->cycle]);
> > >
> > > I think these lines are only needed for Windows (which locks
> > files so
> > > that they can't be overwritten).
> > > I just tested out deleting them, and there is no obvious
> > problem on
> > > Debian. (It may be that in some case of bad LilyPond you get
> > some old
> > > typeset rather than a blank ...)
> >
> > Well this improved the situation but it is not completely
> > fixed. The files are no longer going out of sync but the
> > progressbar window needs closing before Evince can refresh.
> > Its strange that it works properly with exportpdf.
> >
> > Jeremiah
> >
> > >
> > > Richard
> > >
> > >
> > >
> > > On Fri, 2013-12-20 at 11:32 -0600, Jeremiah Benham wrote:
> > > > On Fri, Dec 20, 2013 at 05:20:35PM +0000, Richard Shann
> > wrote:
> > > > > On Fri, 2013-12-20 at 11:10 -0600, Jeremiah Benham
> > wrote:
> > > > > > I created a darwin-x86 build using gub with gtk3 and
> > rubberband. There is a problem that existed in previous mac
> > versions (using gtk2) as well. I upgraded glib thinging that
> > it would fix itself. Here is what I see in denemo:
> > > > > > I launch denemo
> > > > > > I see the progress bar pop-up on top of an evince
> > window
> > > > > > The progress bar seems to be stuck in an infinant
> > loop.
> > > > >
> > > > > There is a possible problem here: when LilyPond is first
> > run it caches
> > > > > its fonts first. On Windows I have seen this take so
> > many minutes that
> > > > > the launch of Denemo appears to have failed.
> > > > > It might be an idea to create a denemorc file to put in
> > > > > the .denemo-1.1.0 directory that contains the preference
> > to not do
> > > > > automatic typesetting (or alter the sources so that it
> > is not the
> > > > > default)
> > > > >
> > > > > <manualtypeset>1</manualtypeset>
> > > > >
> > > > > is the line for this in denemorc.
> > > > >
> > > > > Then at least Denemo should launch and you could start
> > investigating
> > > > > whether it will run LilyPond successfully.
> > > >
> > > > Oh yes. I failed to mention that it does produce pdfs
> > using export pdf. It does this without any problem at all. The
> > progress bar comes up, the progress bar closes on its own,
> > then a pop dialog tells me my pdf has been created. Then I can
> > open the pdf fine using Preview (the default pdf viewer on mac
> > osx).
> > > >
> > > > Jeremiah
> > > > >
> > > > > Richard
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > I kill the progress bar window
> > > > > > Then the evince window refreshes with a blank score
> > > > > > after entering some notes in denemo I focus on the
> > evince window
> > > > > > nothing happens.
> > > > > > I hit refresh in evince...
> > > > > >
> > > > > > Then I get this error:
> > > > > >
> > > > > > alphabeticalizing the commandsVersion 1_1_0
> > > > > > starting to generate LilyPond
> > > > > >
> > > > > > ** (denemo:181): WARNING **: Trying to read the pdf
> > file file:///tmp/Denemo5qMqZo/denemoprintA.pdf gave an error:
> > Error opening file: No such file or directory
> > > > > >
> > > > > > ** (denemo:181): WARNING **: Trying to read the pdf
> > file file:///tmp/Denemo5qMqZo/denemoprintA.pdf gave an error:
> > Error opening file: No such file or directory
> > > > > >
> > > > > > starting to generate LilyPond
> > > > > > This is called when hitting the refresh button while
> > in continuous re-typeset
> > > > > >
> > > > > >
> > > > > > <><><<><><><<><><
> > > > > > Then when I see whats being created in tmp:
> > > > > >
> > > > > > Jeremiah-Benhams-Mac:~ jeremiahbenham$
> > ls /tmp/Denemo5qMqZo/
> > > > > > denemoprintA.ly denemoprintB.pdf
> > > > > > denemoprintB.ly denemoprintB.ps
> > > > > >
> > > > > >
> > > > > > Jeremiah
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Denemo-devel mailing list
> > > > > > address@hidden
> > > > > > https://lists.gnu.org/mailman/listinfo/denemo-devel
> > > > >
> > > > >
> > >
> > >
>
>
| [Prev in Thread] | Current Thread | [Next in Thread] |