[Scilab-users] Problem with clip_state

[Federico Miyara]

OF, I have now filed it as a bug. Thenk you.

Regards,

Federico

On 06/04/2019 14:39, Samuel Gougeon wrote:
> 1) I create new axes by plotting some data set. As expected, axes' 
> size matches the plot data range.
>
> 2) I run
>
> gca().clip_state = "off"
>
> Acording to the documentation  
> (https://help.scilab.org/docs/6.0.2/en_US/axes_properties.html), from 
> now on all newly created objects should not clip, meaning that even if 
> the object (such as a polyline) exceeds the original data range, it 
> will be displayed in full.
>
> 3) I plot another data set that exceeds the original axes limits. 
> Contrary to the expected behavior, it does clip.
>
> 4) I run
>
> gca().clip_state
>
> and I see it has reverted to "clipgrf". This explains the observed 
> clipping, but it is not clear why the setting from 2) has changed.
>
> 5) I run again
>
> gca().clip_state = "off"
>
> Nothing happens (it makes sense, since the clip_state should affect 
> new objects, not previous ones)
>
> 6) I run
>
> gce().children.clip_state = "off"
>
> Only now the clipping is gone and the second plot shows in full. 



---
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20190406/8f79bbf6/attachment.htm>