Aha, that explains the difficulty in reproduction. Glad you were able to get it going.

That’s helpful!I’ll look into it.Thankssasha

Thanks for the report. We’ll take a look at it!Does it work for you in the simulator?sasha

Ah, I believe that documentation is out of date.As of AIR 3, front-facing camera should work on both Android and iOS.

Hi, Josh,There are two answers to that question: 1. There is a beta version of the LCCS framework that is mobile compatible. http://forums.adobe.com/message/3833841#3833841#3833841 2. you can create a mobile app using the Flash-only SWC included in the release LCCS SDK.Thankssasha

Well, assuming the problem lies in the disconnect between your null check and the actual state of the lobbyView variable, I might try making the check explicitly for null, so if (lobbyView != null) rather than if (lobbyView). Not that these shouldn’t be equivalent in this case, but I’m not sure what else could have changed between player 10.3 and 11. I’ll also try to ask around the runtime team and see if they have any ideas.sasha

Thanks, Alex,Sounds like you’ve done quite a bit of research into this already. However, I think I’m confused.lobbyView is null when it should not be? Or it’s not null even though you set it to null? Or it’s null, but your checks (lobbyView != null) to ensure that you don’t access a null variable aren’t working correctly?Thankssasha

Hi, Alex, assuming I understand the problem correctly, I cannot reproduce it. A few questions: 1) How are you setting the targeted player? 2) I take it you're using the Player10 LCCS swc?3) Which version of the Flex SDK are you using?4) do non-LCCS UI elements show up?5) Mac or Windows or both? Have you tried on more than one browser? thankssasha

Hi, Glenn. We don't have an outward facing bugbase for LCCS, so please just report bugshere. Incidentally, to solve the issue you mentioned above, if I understand itcorrectly, you should be able to just add the following line at the end ofRichTextArea.set htmlText dispatchEvent(new Event("htmlTextChanged"));Thankssasha

Hi Glenn, Nothing else's been released. There's no secret program or private group oranything. We've been working on this in the background while waiting forfeedback from the forums. Your bug has been noted, and we'll fix it.We don't have a date for the next release. As soon as we do, we'll let youknow. In the meantime, if you can let us know any other issues you see thatwe've not listed it'd be great, so we can make sure we address them.Thankssasha

The Flash CS5 Authoring tool does not support 10.3 officially. However, as Idetailed earlier, with a couple steps you can update the application totarget Flash Player 10.3. Flash playback is of course fully supported.sasha

OK, Keep in mind that I'm pretty sure authoring for 10.3 is not officiallysupported in Flash CS5. However, the following steps seem to work:1. in your {Flash install}/Common/Configuration/Players folder, you'll see aFlashPlayer10_2.xml file.2. Duplicate that file and rename it FlashPlayer10_3.xml3. Open the new file and change the line starting Publish Settings. There should now be a Player 10.3 itemavailable in the Player dropdown.You should now be able to use 10.3-specific APIs. However, I bel...

If you are compiling from the command line, you can add the argument -swf-version=12 to your compiler callIf you are using Flash Builder, you'll need to right click on the project, Choose Properties, and select Flex Compiler. Add -swf-version=12 to the Additional Compiler Arguments text box.thankssasha

Not as far as I know. I'll see if I can find out anything from the Runtimeteam about it.

Hi, Suha, we do not currently have a mobile-compatible version of the LCCSSDK. We'll be releasing a beta version of one quite soon, however.Thankssasha

Hi, Joseph, I'm not sure exactly what you're asking here. Can you be more explicit aboutexactly the use case you're trying to enable?ThanksSasha

There's not currently any support for addressing the WhiteBoard toolbar fromExternal Interface. You'd have to extend either SharedWhiteBoard orEditorToolBar, I think.

Well, if you're not seeing any stop/start button text, it seems likely thateither the component is not getting added to the stage or it's being locatedor sized incorrectly. I'd suggest that you ensure it's all being initializedcorrectly by debugging into the constructor and the setBackGround methods.Thankssasha

If there's nothing appearing on screen, it seems possible that you have not added the FlashWebCamExample class to the stage.DO you have a default view in your application?Did you add the first block of code I mentioned in this message: http://forums.adobe.com/message/3765114#3765114 to it?Here's the full code of the default view in my test app: import mx.core.UIComponent; private var flashCam:FlashWebCamExample; private function addCam():void { flashCam= new FlashWebCamExample(); var ui:UIComponent = new UIComponent; addElement(ui); ui.addChild(flashCam); } If you've already got this in your default view, I suggest you put a breakpoint in the addCam() method and make sure it's getting called.

Are using the Simulator, or are you trying this directly on a device? Do yousee a stop/start button on stage to click?

Ofer, are you sure you're using the Flash Only version of the LCCSlibraries? Because there should not be any mx components referred to at all.So either you have used a label in whatever app you are creating, or (morelikely) you're using a flex version of the LCCS libraries. Please check tomake sure you're compiling against the SWC incom.adobe.lccs/libs/flashOnly/player10.1/lccsFlash.swcThankssasha