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

Home » Public Forums » archive » Re: weird font issue: string("305B) does not work any more?
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: weird font issue: string("305B) does not work any more? [message #61155 is a reply to message #61149] Sun, 06 July 2008 07:09 Go to previous message
David Fanning is currently offline  David Fanning
Messages: 11724
Registered: August 2001
Senior Member
biophys writes:

> It's been a long time since last time I used something like
> string("305B) to get these special characters. However, this time it
> doesn't work for me on a windows machine with direct graphics. If I
> use
>
> IDL>!p.font=-1 & XYOUTS,.1, .5, '!3Here is an Angstrom symbol: ' +
> STRING("305B), /NORM, CHARSIZE=3
> or
> IDL>!p.font=1 & XYOUTS,.1, .5, '!3Here is an Angstrom symbol: ' +
> STRING("305B), /NORM, CHARSIZE=3
>
> the angstrom does not show up.

As far as I know this has never worked with direct graphics
and hardware fonts. In fact, I don't see how it could.

Cheers,

David

--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. ("Perhaps thou speakest truth.")
[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: Getting mean from HDF SD files - stack in envi or read into IDL array?
Next Topic: Failed Launching IDLDE 7.0 after CentOS upgrade

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

Current Time: Sat Oct 11 15:26:33 PDT 2025

Total time taken to generate the page: 0.00876 seconds