$cinst.$class of a subwindow - 2

[Terence J. Young, D.C.]

Hi,

You can also try removing the $construct method, if any, from behind the 
second subwindow field of the parent window; perhaps this is conflicting 
with the scope of the code executing within the $construct method of the 
subwindow.  Methods placed behind the subwindow field of a parent window 
have a special relationship with the subwindow instatiated within them; 
the methods can be called from within the subwindow as though they were 
public methods within the subwindow themselves.

terry

omnislist at dataweaver.com wrote:
> Hi $all,
>
> I have a generic line in my $construct, which assigns a popup menu to 
> a headed list as follows:
>
> Do irListHeaded.$contextmenu.$assign(con('mpop',$cinst.$class().$name))
>
> If a popup menu exists in the form 'mpopWindowName' then this works 
> fine...or doesn't in some cases!
>
> I have two subwindows on a parent window, 'WindowParent'.
> One is called 'WindowA', the other 'WindowB'
> There are two popup menus in the library: 'mpopWindowA' and 'mpopWindowB'
> When WindowA is instantiating, $cinst.$class().$name returns 'WindowA' 
> but when WindowB is instantiating, this returns 'WindowParent'.
>
> Funny thing is, if I set a reference to $cinst, the reference seems to 
> point to the subwindow, WindowB. However, itemReference.$class() still 
> returns the parent window name.
>
> Any ideas?
>
> Rgds
> Gav
>
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
>
>