comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: IDL 6.1 EPS error
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDL 6.1 EPS error [message #41479 is a reply to message #41478] Wed, 27 October 2004 15:29 Go to previous messageGo to previous message
Michael Wallace is currently offline  Michael Wallace
Messages: 409
Registered: December 2003
Senior Member
> IDL 6.1 has some significant bugs in its EPS output. (I don't think the
> behaviour you have described resembles any of the bugs I am aware of,
> but still...) I understand these are to be fixed in 6.1.1, which was
> announced by email on 2 October as a fix for problem in "reading
> non-finite data in IDL 6.1", but will also fix a few other problems. It
> is to be released in "a few weeks".


I've found the specific culprit of my problem. I should have thought to
look at the actual EPS code created, but it didn't dawn on me until now.
The EPS code is writing nan's to the actual EPS file. This only
happens for my text objects and always follows the same pattern.

/Courier findfont 13.9875 scalefont setfont
()
nan nan M T


It appears that RSI attempted to update the EPS format in the move from
6.0.3 to 6.1. EPS files created with 6.0.3 show "%!PS-Adobe-2.0
EPSF-1.2" while files created with 6.1 show "%!PS-Adobe-3.0 EPSF-3.0".
And the actual EPS code looks wildly different between the two. So, I
guess it's back to IDL 6.0.3 for the time being.

-Mike
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Field of View
Next Topic: fft_comparison.html (question to David Fanning and Paul van Delst)

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 09:24:31 PDT 2025

Total time taken to generate the page: 0.96412 seconds