6 Replies Latest reply: Jul 22, 2011 11:07 PM by ewong2011
ewong2011 Level 1 (0 points)

I will have the Facetime app on, have a conversation with a person. I have Mail opened up full screen in another "space." When I switch to that space, the camera turns off. I have to go back to the "space" that FaceTime is in in order to turn the camera back on. Is there a way to keep the camera on all the time when switching between different spaces and the Dashboard?


FaceTime, Mac OS X (10.7)
  • cmags Level 1 (10 points)

    Having the same problem - In Snow Leopard, when I was on a FaceTime chat with a friend, I was able to navigate away from the FaceTime and surf, check the calendar and other stuff without pausing my video feed. In LION, for whatever reason, FaceTime pauses itself whenever I navigate away from the app. It's as if the application is FORCING me to stay in the conversation when, sometimes, I use FaceTime for TALKING, not VIDEO CONFERENCING.

  • cmags Level 1 (10 points)

    The work around I just figured out is to assign FaceTime to every space.  That wasn't needed on Snow Leopard with FaceTime 0.9, but apparently that's what you have to do now to be able to multitask while FaceTiming.

  • ewong2011 Level 1 (0 points)

    cmags,

     

    How would you go about doing this? I remember it was a simple method to do in Snow Leopard, but in Lion, it seems very complicated on how to do this.

  • cmags Level 1 (10 points)

    Yeah, they didn't make it obvious in Lion, but just right click on the app icon in the dock and got to "options".  Under there you'll see "Assign to" options and one of them is "All Desktops".  I do this for the Finder as well. 

  • ewong2011 Level 1 (0 points)

    I actually don't have that option. When I go to "options" it only gives me "Remove From Dock," "Open at Login" and "Show in Finder." That's with all of the apps in my dock also.

  • ewong2011 Level 1 (0 points)

    I actually had to open a new "Desktop" in Mission Control in order to get the option for "Assign to"

     

    It seems like the best workaround right now.