> If you are using a nested fuseaction, you have to suppress
> layouts "above" the nested fuse's layout. You will need to
> put code in fbx_layouts to avoid this by checking
> $fusebox{"isNestedCall"}, or an easier way is to set
> $fusebox{"nestLayouts"} := false in the display circuit of
> the nested fuseaction.
>
> Regards,
>
>
Aparajita,
My environment is Active4D 3.0.1 b7, 4D 2003 Server on a Win2000 server. I
haven't needed to use $fusebox{"isNestedCall"} or $fusebox{"nestLayouts"}
prior to this site update, so I'm not sure if I was using nested calls
before or not, I am using the same code that worked before I changed the
html(for look & feel reasons only) code in my layouts. I tried displaying
the value of $fusebox{"isNestedCall"} on the form to see what it is, but it
must be a data that gets set in the newer implementation of fusebox. I
guess the biggest confusion is what else could have changed? The old site
has several nested circuits with fuseaction calls throughout and they never
duplicated before.
Sincerely,
Mike Vogt
Millennium Data Services, Inc.
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
