|
From: | Michael D Godfrey |
Subject: | Re: fltk printing |
Date: | Sat, 07 Aug 2010 11:33:51 -0700 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100720 Fedora/3.1.1-1.fc13 Thunderbird/3.1.1 |
On 08/07/2010 11:08 AM, Shai Ayal wrote:
I was partly wrong about the server point. Of course, the /tmp files are local, but theMichael, I'm surprised the temp files are on a server? Does tmpnam() actually return a file to be opened on a server?In either event, it does appear to be a synchronization / timing problem. Reading through the Matlab docs, if new files are created programmatically they will not be seen by Matlab until the next command prompt. To overcome this "rehash()" should be run. I'm not familiar with what Octave does in this case, but it looks quite similar. Explicitly updating the path looks like a better solution than using a while-loop and waiting until Octave sees the file. Shai, Is "rehash" implicit when "drawnow ("eps", opts.name)" is called? .,, should it be?Are you sure rehash is the correct command to use? from the help text it "Reinitializes Octave's load path directory cache". Why is this connected to the file appearing in octave? Shai result file goes to the NFS server. Ben pointed out what appears to be a real timing problem, and his patch seems to have it fixed. Part of the problem was in __fltk__print__.m We should find out what rehash() actually does. Also, it would be good to determine exactly why print('test.pdf') works and print test.pdf does not. I will try to learn more about this. Michael Michael |
[Prev in Thread] | Current Thread | [Next in Thread] |