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

Home » Public Forums » archive » object graphics, exploding axis text, how to fix by explicitly setting char_dimens?
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: object graphics, exploding axis text, how to fix by explicitly setting char_dimens? [message #86777 is a reply to message #86733] Mon, 02 December 2013 13:05 Go to previous messageGo to previous message
jkj is currently offline  jkj
Messages: 48
Registered: April 2007
Member
On Friday, November 29, 2013 3:30:52 PM UTC-6, jkj wrote:
> On Friday, November 29, 2013 3:16:44 PM UTC-6, David Fanning wrote:
>
>> jkj writes:
>
>>
>
>> I suppose another possibility is that OpenGL is to blame. I'd be curious
>
>
>

I'll update this if anything changes but there are two issues in play here: IDL version and my thumbprint!

two-dimensional plots have 'exploding text' only if IDL 5.5 is used [hedging a bit here because I'd have sworn I've seen cases with 8.2]

three-dimensional surfaces have 'exploding text' on the z-axis and in submitting a ticket for ExelisVis it became clear that there is an error in how I am implementing "layered/phantom axes" [funny how preparing material for troubleshooting assistance generally leads one to the solution!]

the first set of axes is used to build the surface but the data displayed would simply be grid values [0->200 for a 200x200 grid] and we want to display the science data, so the surface is built with indgen() arrays for x/y data and then 'phantom axes' are built with the science data... somehow in that process I am fumbling because if I turn off the science data axes there is no exploding text and with the science axes on I can see evidence of confusion in the x/y/zrange values (which, of course, can not be explicitly set for 'idlgraxis')

anyway, I'll figure out how to wipe away my thumbprints and that should resolve this... the whole thing has been a bit quirky and intermittent enough that I still won't be surprised to find another element but I definitely think I'm the culprit in all of this
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: plotting x-y error bars in IDL
Next Topic: peak finding with Guassfit

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

Current Time: Thu Oct 09 00:39:49 PDT 2025

Total time taken to generate the page: 0.56255 seconds