This seems like a pretty easy change to make. If Adobe devs turn out to
be too busy to do it, any chance you would accept the code from an
external developer (and LCCS user) to get this pushed into the console?
I'd be happy to code it up if it would help myself and others.Edit:
Mis-read the original post. Corrected misinformation in my reply.
The Room Console is a pretty nice tool to have out of the box to aid in
visual debugging of LCCS room-state. However, I think it would be far
more usable if the list of "My Rooms" were sortable and searchable. Once
that list gets full it can be a huge pain to find a single room.
Right, I was just not suggesting we could "catch" it so much as listen
for it (in an error-Event).In either case, glad to see it's on the radar
for a short-term fix. That's awesome. Thanks for the update, Nigel.
I am unable to install the LCCS "SDK Navigator Application" from the
LCCS Developer portal. When I try to run the AIR installer, I get the
following error message:Sorry, an error has occurred.This application
cannot be installed because this installer has been misconfigured.
Please contact the application author for
AIR.framework/Versions/Current/Resources/Info.plist shows my AIR
"CFBundleVersion" is "126.96.36.19940".
I'm with Marc on this one. Throwing an error that can't be listened to
(short of a global error handler) seems like bad practice.(We just
encountered a similar error and I found this forum thread while Googling
You don't need to wrap the authenticator in a Declarations tag. It just
can't be added to the display list. As it is in the example, it's not
being added to the display list- it's just being assigned to the
ConnectSessionContainer's "authenticator" property.You could add an
event listener to see if you were ever actually getting into the
room...That's the lightest-weight way to do it. If you don't see the
"synchronizationChange" message in your console you'll at least know a
I can second that there is no Flex 4 + ConnectSessionContainer
issue.Also, for what it's worth, the following code works fine for me
(with pods inside or outside of the
So no issue with *Box
components. My guess is, if you're seeing a white screen, your room
connection/authentication is hanging? Sure nothing weird is happening
concurrently (like someone else in the room that's causing troubles with
your role, etc) ?