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

Home » Public Forums » archive » Re: IDLgrAxis and scaling
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: IDLgrAxis and scaling [message #34486 is a reply to message #34485] Wed, 19 March 2003 18:02 Go to previous messageGo to previous message
Thomas Gutzler is currently offline  Thomas Gutzler
Messages: 44
Registered: November 2002
Member
Mark Hadfield wrote:
> "Thomas Gutzler" <tgutzler@ee.uwa.edu.au> wrote in message
> news:3E783423.4080505@ee.uwa.edu.au...
>
>> Hi,
>>
>> I tried to prevent the axis-text to be scaled while scaling a model with
>> the axes added.
>
>
> This is controlled by the RECOMPUTE_DIMENSIONS property of the axis-text
> IDLgrText objects. Default is 0; you should use 1 or 2

Yeah, that's what I thought, too.

Where is the difference between this:

> self->GetProperty, TICKTEXT=oticktext, TITLE=otitle
> for i=0,n_elements(oticktext)-1 do begin
> if obj_valid(oticktext[i]) then begin
> oticktext[i]->SetProperty, $
> RECOMPUTE_DIMENSIONS=self.recompute_dimensions
> oticktext[i]->GetProperty, FONT=font
> if not obj_valid(font) then $
> oticktext[i]->SetProperty, FONT=self.font
> endif
> endfor

and that:
zaxis->GetProperty, Ticktext=text
text->SetProperty, Recompute_Dimensions=1

I think there is none. The difference is somewhere else:
In MGHgrAxis::Init:
self.recompute_dimensions = $
n_elements(recompute_dimensions) gt 0 ? recompute_dimensions : 2
^
Setting Recompute_Dimensions=2 instead of 1 solves it.

Thanks for that.

Tom
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Error compiling procedure already compiled
Next Topic: Re: Ctrl-C keyboard event missing

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

Current Time: Wed Oct 08 18:38:59 PDT 2025

Total time taken to generate the page: 0.00411 seconds