[Scilab-Dev] Problem/missing feature with uicontrols

[Stéphane Mottelet]

Le 17/06/2010 11:43, Vincent COUVERT a écrit :
> Hi Stéphane,
>
> These two problems are bugs (an not features) reported in Bugzilla:
> http://bugzilla.scilab.org/show_bug.cgi?id=5477
> http://bugzilla.scilab.org/show_bug.cgi?id=7090

Ok, but for #5477 it is a different issue concerning the convention about
the position of the (0,0) origin for uicontrols, which should be
on upper left corner of figure.

S.

>
> We will fix them as soon as possible.
>
> Vincent
>
> Le 16/06/2010 17:48, Stéphane Mottelet a écrit :
>> Le 16/06/2010 17:07, Stéphane Mottelet a écrit :
>>> Hi all,
>>>
>>> There is a missing (easy to implement) feature in uicontrols.
>>> When you create e.g. a button as a children of a frame, when
>>> making the frame invisible, the button should also dissapear,
>>> regardless of its 'visible'  property. Actually, this is not the case
>>> (at least in Scilab 5.2.1). This is very annoying, since in Tk
>>> the visible state is inherited by childrens. Try the following
>>> piece of code :
>>>
>>> f=uicontrol('style','frame','position',[0 0 100 200]);
>>> b=uicontrol(f,'style','pushbutton','position',[0 0 100 
>>> 20],'string','push me');
>>> set(f,'visible','off');
>>>
>>> S.
>>>
>>>
>> I am sorry, but I discovered worse things : the "position" property is
>> relative to the parent at creation time, but when you move a widget
>> by changing its position, then children stay stuck on the root window.
>> See the example code :
>>
>> f=uicontrol('style','frame','position',[100 100 100 100]);
>> b=uicontrol(f,'style','pushbutton','position',[0 0 100 
>> 20],'string','push me');
>> f.position=[0 0 100 100]
>>
>> Is it a bug or a feature ?
>>
>>
>> S.
>