Thanks Eric. I'll give it a shot,
Mark
On 1/6/07, Eric Firing <[EMAIL PROTECTED]> wrote:
Mark Bakker wrote:
> Eric -
>
> Yeah, I agree. The words 'equal' is confusing. But it was taken from
> matlab. 'scaled' was my invention/doing. I thought it was better than
> 'equal', as it makes the scales
Mark Bakker wrote:
> Eric -
>
> Yeah, I agree. The words 'equal' is confusing. But it was taken from
> matlab. 'scaled' was my invention/doing. I thought it was better than
> 'equal', as it makes the scales equal on both axes. Either way, I would
> like it if we can fix the data limits in a sim
Eric -
Yeah, I agree. The words 'equal' is confusing. But it was taken from matlab.
'scaled' was my invention/doing. I thought it was better than 'equal', as it
makes the scales equal on both axes. Either way, I would like it if we can
fix the data limits in a simple way, and I think incorporatin
Mark Bakker wrote:
> The enhanced way of handling aspect ratios that Eric implemented works
> great.
> There is, however, one change from the old implementation that I don't like.
>
> In the old implementation, when setting axis('scaled') it also turned
> autoscale off.
> This makes sense (and I
The enhanced way of handling aspect ratios that Eric implemented works
great.
There is, however, one change from the old implementation that I don't like.
In the old implementation, when setting axis('scaled') it also turned
autoscale off.
This makes sense (and I used it a lot). It means that you