ok, its good to know that it is not simply something that we are doing on our end that is causing the issue. Although I am confident that your suggestion would work, it seems like a huge amount of effort to go through to address the issue.

You may want to think about using a canvas with a resize event: layout goes hereAnd then resizing your layout programatically, something like:private function resizeScreenComponents():void{ control.width = pageContainer.width *.5; control.height = pageContainer.height * .5; ...}

Here is a sample that will do what you want. You can still get a single scroll bar occasionally when you really skew the viewport dimensions, but for the most part, this does the best job of utilizing the available space. Not sure why your code does not do it, like I said before, you have a lot of nested layout regions in there. It may be simpler for you to start with an example that works, and then add the rest of your bits back in. import com.adobe.rtc.collaboration.ScreenShareSubscriberComplex; private function init():void{ var sss:ScreenShareSubscriberComplex= new ScreenShareSubscriberComplex(); sss.connectSession = cSession; sss.percentWidth = 100; sss.percentHeight = 100; sss.x = 0; sss.y = 0; displayArea.addChild(sss); }

You need to make sure that the parent container also has widths specified in % values (ie):if you still have problems, you may want to move your parent container to the root level of your layout temporarily until you get it working correctly.

When you intialize the ScreenShareSubscriberComplex, you just need to set the percentWidth and percentHeight (like below). If you just assign widths to your parent container, you will get scroll bars, because the subscriber component won't resize with its container. sss = new ScreenShareSubscriberComplex(); sss.connectSession = cSession;sss.percentWidth = 100;sss.percentHeight = 100;sss.x = 0;sss.y = 0;sss.showMyStream = true; displayArea.addChild(sss);Hope that helps,John

I said in my original post that the Room Console would create the template with the correct settings but it wasn't working through the server to server api.I have tried it again this morning however, and it is now working as expected (wierd because I did not change anything from last night). Is there some sort of propagation or caching that occurs when you change settings in an exisiting template, or should I expect the new settings to always take effect immediately?Regardless, it seems to be wo...