Wed 06 Apr 2011 01:49:00 PM UTC, comment #10:
A new windows version is out - this is very close to release now, please test.
|
Tue 05 Apr 2011 07:30:48 PM UTC, comment #9:
Sorry, it looks like my version is from Feb 28 as that's the time on the denemo.exe. I don't know if this problem is fixed or not on current git.-DW
|
Tue 05 Apr 2011 08:30:18 AM UTC, comment #8:
Jeremiah, I think you have mis-read the code at this point.
I have already done the fix you intended to do, that is what the
#ifndef G_OS_WIN32
is doing there in print.c at the point where you have put in a #if 0.
This is the commit I did:
Do not test for status of LilyPond on windows, as it appears not to work
author Richard Shann <rshann@debianrts.home>
Thu, 17 Mar 2011 17:32:55 +0000 (17:32 +0000)
committer Richard Shann <rshann@debianrts.home>
Thu, 17 Mar 2011 17:32:55 +0000 (17:32 +0000)
commit a42aea1aed688f06c1a42d7bc7b1dd99e9eb614a
tree 483d6829e74e62d32352c1e34f66d42292732c33
parent 57ef245f9f1dbd70278f28f66d894151ba8cc697
I seem to have failed to put a note about this fix into this bug report - sorry. DanW is your build from a git post 17th Mar?
Jeremiah - can you revert your change please as it is removing the check for all o/s?
|
Mon 04 Apr 2011 09:22:53 PM UTC, comment #7:
In the latest git I commented out the win32 status check. I saw a comment saying that this was failing to work anyway. Let me know if this fixes things. If status had the wrong value it could have exited before launching the viewer. I hope this fixes it. I would have to get gub working to try this out myself.
|
Sun 03 Apr 2011 11:41:48 PM UTC, comment #6:
Sorry I didn't reply sooner to this.
My most up-to-date denemo still has this problem, but I'm not sure how long ago it's from.
This was definitely NOT a lilypond failure. I know this because I can go to the .denemo directory, and there is a perfectly fine denemoprint.pdf that I can open and see the score as it should look.
If the problem was not in the missing ".pdf" from denemoprint when trying to open it, then I don't know what's wrong either. But it's definitely not a problem with lilypond processing.
-Dan W.
|
Wed 02 Mar 2011 08:57:43 PM UTC, comment #5:
printf was printing the wrong information. So this is incorrect:
"Opening filename = C:\.....\.denemo\denemoprint"
I don't know where it is going wrong. You first wrote:
But denemo says that "Lilypond engraver failed..."
That means lilypond is failing not the loading of the pdf.
Have you tried taking the resulting .ly file in your .denemo dir and running lilypond on it to find out if that is the case.
|
Wed 02 Mar 2011 08:29:11 PM UTC, comment #4:
Testing this with a score containing a single whole note fails just as before.
-Dan W.
|
Wed 02 Mar 2011 09:44:18 AM UTC, comment #3:
"Opening filename = C:\.....\.denemo\denemoprint"
if that is the case, ie there is no trailing .pdf then the attempt to "open" will fail on windows, where the .pdf has to be present for the file association to work.
|
Wed 02 Mar 2011 01:00:31 AM UTC, comment #2:
I can test this tomorrow, probably. (I'm away from the machine with the current denemo on it)
The score I tried was pretty simple, though, just a few notes to test the tempo with bpm syntax for lilypond 2.10.
-DW
|
Tue 01 Mar 2011 10:43:44 PM UTC, comment #1:
does this happen with even the simplest of scores. That message you received was not correct. I modified the code to print out the correct information. I think it failed before this though. Can you test again with a simple one note score?
|
Tue 01 Mar 2011 08:05:33 PM UTC, original submission:
Not sure why, but now when I click print preview, Lilypond processes the score fine, and the pdf is generated properly inside .denemo directory. But denemo says that "Lilypond engraver failed..." and the pdf does not appear. It must be a problem with opening the pdf reader.
The console says "Opening filename = C:\.....\.denemo\denemoprint"
Shouldn't this be "...\denemoprint.pdf"?
-Dan W
|