Pop-out panels into new windows — Microsoft Flight Simulator 2020

Learn how to put the panels and information readouts into a new window in Microsoft Flight Simulator 2020.

As players take to the skies in Microsoft Flight Simulator 2020, some are wondering about how to pop-out the panels into new windows. The advantage of this would be in having the information displayed in a larger format, big multi-monitor setups, or some other personal preference. While there are certainly a lot of keys and buttons to remember, popping out the panels and moving them around is a breeze.

Pop-out info panels into new windows

Microsoft Flight Simulator 2020 has a lot of controls and keybindings. Unfortunately, it’s not always super easy to work out some of the finer adjustments one might want to make. In order to pop-out the panels in your airplane’s cockpit and into new windows, players must first ensure they are in the pilot’s seat. Once in your plane of choice, do the following:

1. Hold Right ALT
2. Mouseover the panel you want to pop-out to see a magnifying glass
3. Left-click the panel to pop-out
4. The panel’s display will appear in a new window

While the panels and readouts look good, sometimes they’re tough to see. There is a way to pop these out and into new windows for better viewing.

To pop-out multiple panels and have them in separate windows, perform the above steps on all panels you want. Next, do the following steps:

1. Mouseover the new pop-out window
2. Click the magnification icon in the top-right corner of the panel’s display
3. The screens will now be separated into individual windows

This helpful tip comes by way of Reddit user warwolf09. This is a great method for players to put the screens in the cockpit into new windows. Instead of having the information on a single screen, this method allows for players to put critical information on other monitors, creating a true multi-monitor setup.

Now that you’ve got panels and readouts popped out and in new windows, make sure you spend some time with the Shacknews Microsoft Flight Simulator 2020 guide. This is an ever-evolving collection of information that will help you conquer the skies.

Hailing from the land down under, Sam Chandler brings a bit of the southern hemisphere flair to his work. After bouncing round a few universities, securing a bachelor degree, and entering the video game industry, he’s found his new family here at Shacknews as a Guides Editor. There’s nothing he loves more than crafting a guide that will help someone. If you need help with a guide, or notice something not quite right, you can Tweet him: @SamuelChandler

Teams Pop-Out Windows for Chats and Meetings

Popping Out Teams Windows

Updated May 10 with information about pop-out window support for meetings.

Office 365 notification MC207218 posted on March 21 confirmed the news shared in Microsoft’s What’s New in Microsoft Teams 3rd anniversary edition announcement that the Teams desktop client has its first pop-out window, but only on Windows (Microsoft 365 roadmap item 57292). According to a clarification posted by Microsoft on March 23, they will “provide support for Mac and Linux clients in the coming weeks.” The roll-out to Office 365 tenants begins in early April and should complete to all tenants worldwide by the end of May.

On May 9, Microsoft posted MC212453 to announce multi-window support for calls (Microsoft 365 roadmap item 57294). This feature will roll out in multiple phases (see section below).

Multi-Window Support

Since the introduction of Teams everything has been done inside a single multi-paned window and the only way to have multiple windows for Teams has been to create multiple browser tabs or windows. Now, the desktop client can pop-out window for personal (1×1) and group chats and (soon) meetings. Pop-outs aren’t supported for channel conversations. You can’t pop-out a personal chat in the Teams browser client.

Microsoft is keen to emphasize that multi-window support enables users to multitask more efficiently by dividing work across multiple windows and “more easily move between ongoing conversations.” In practice, the feature is particularly helpful when you need to keep an eye on a chat while working in another area in the client, such as viewing a document or composing a salient response to a topic in a channel. It’s also a popular request in Teams User Voice.

Popping a Teams Chat

You can pop-out a chat window several ways. First, find someone you want to chat with in your chat list and either double-click a chat or select the Pop-out chat option from the […] menu or the fly-out icon (Figure 1). The option is available for 1×1 chats with federated users in other Office 365 tenants and Skype consumer users.

Alternatively, the same fly-out icon is available in the top right-hand corner of a chat (Figure 2).

You can also use the /pop command in the command bar to search for a user and pop-out a window to chat with them (Figure 3). This is probably how power users will use the feature.

In all cases, the window created for the pop-out chat. As you can see in Figure 4, you can take the same actions as are available in the chat pane in the desktop client.

Multi-Window Meetings

Microsoft plans to deliver multi-window support for Teams meetings (Figure 5) in several phases starting in June 2020 (the timeline is subject to change).

• June: Multi-window support for meetings is disabled in the Teams client and must be enabled by the user through the General section of Teams Settings.
• July: Multi-window support for meetings is enabled by default. If they prefer to use the old experience, users can disable multi-window support through Teams settings.
• August: Multi-window support for meetings becomes the norm for Teams and the control to enable or disable the option is removed from Teams settings.

Update September 5: According to an update (MC212453) published by Microsoft, October is the new target date for the complete switchover to the new meeting experience.

When multi-window meetings are enabled, Teams automatically creates a new window each time you join a meeting.

In addition, Microsoft is moving the meeting and call controls (mute, recording, hands up, chat, leave, etc.) to the top of the meeting window (Figure 6) to make better use of screen real estate. Microsoft says that the move also makes sure that controls don’t block underlying content. The new pop-out window supports newly announced features like background effects and 3 x 3 view.

Disabling the New Experience

If you don’t like the new pop-out windows, you can disable them in the General section of Teams settings (Figure 7). You’ll have to restart Teams afterwards to revert to the old behavior.

Although user interface changes like this don’t usually make it into the pages of the Office 365 for IT Pros eBook, we thought that this update was interesting enough to bring to your attention.

5 Different Ways to Pop-out Your Chats in Teams

by Brian Siefferman on May 25th, 2020 |

The pop-out chat capability just showed up in my Teams client this week. If your client hasn’t received this yet, you should be receiving it by the end of this month (May)! Pop-out chat allows you to pop out your one-to-one or one-to-many (group) chats into a separate window. If you’re coming from Skype for Business, you are probably very familiar with this feature. This will help with multitasking while you’re in a meeting or in a call by allowing you to pop out multiple conversations. In today’s blog, I’ll show you the 5 different ways you can pop-out a chat so you can utilize this feature to its fullest potential.

Pop-out a chat

There are actually 5 different ways you can begin using the pop-out chat:

1. From the chat list
2. From the chat itself
3. From a profile picture
4. By hovering over a chat
5. From the command box

From the chat list

To pop the chat out from the chat list just follow these steps:

1. Select your Chat icon on the left-hand side of your Teams client to open the chat list.
2. Find the name of the person/people you want to chat with.
3. Once you’ve found the user select More options ‘…’ > Pop-out chat. Or, just double-click on the name of the user and you’ll see a new pop-out chat window.

From the chat itself

1. Select your Chat icon on the left-hand side of your Teams client to open the chat list.
2. Find the name of the person/people you want to chat with.
3. Go to the top right corner of the chat and select Pop-out chat.

The Essential Guide to Microsoft Teams End-User Engagement

We take you through 10 best practices, considerations, and suggestions that can enrich your Microsoft Teams deployment and ensure both end-user adoption and engagement.

From the profile picture

1. Find the person you want to have a conversation with and double click their profile picture.
2. BOOM…New Window!

By hovering over a chat

1. Select your Chat icon on the left-hand side of your Teams client to open the chat list.
2. Find someone in your chat list that you would like to chat with.
3. Hover over the chat and select Pop-out chat.

From the command box

1. In the command box, type /pop
2. Pick the chat you want to pop out.

There you have it, 5 different ways to pop-out your chat in Microsoft Teams. There are a few final tidbits to mention:

1. The pop-out chat capabilities are only available for Windows and Mac clients at this time. This is not yet supported by Linux or mobile clients.
2. You can pop-out multiple chat conversations, just not the same chat twice.
3. If you want to do things like schedule a meeting, attach a file, or add an app, you’ll need to go back to your main chat app within the client to perform these functions. However, this does not mean you need to close the pop-out chat window when doing this, it can remain open without this causing any issues.
4. You cannot currently pop-out calls or meetings at this time. However, this is just on the horizon and is slated for release in June!

I hope you have found this quick rundown on pop-out chat helpful, stay tuned for future blog posts on some of the great new features and functionality that Microsoft will be rolling out over the next few months. It is an exciting time to be using Teams, so don’t miss out on all it has to offer!

About the Author

Brian is a Technical Consultant for Perficient’s Unified Communications practice focusing primarily on Skype for Business and Microsoft Teams workloads. He has been in this role since December 2017 and has an active presence blogging about all things Teams related. Currently, Brian resides in the suburbs of Chicago and enjoys running, swimming, weight lifting, and playing soccer in his free time.

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Developers: Tap into the full potential of pop-out windows

Developers: Tap into the full potential of pop-out windows

Could I establish a deeper level of communication between pop-out windows and their parent pages? The standard ways of communicating additional information to users are either modal dialogues–dialogues residing on the same page, or pop-up windows–pages rendered in a new browser window. Most implementations of pop-up dialogues involve having a separate page with logic to render the whole body alongside business logic.

Recently, I determined that there is no need for a separate page. In a nutshell, the strategy I developed involves housing the logic of the main page and pop-out window in the same browser window. In this blog entry, I reveal how I did it.

The nuts and bolts

In part to avoid the pitfalls of using a rigid bundling and hosting framework (I’m talking about you, webpack), I used the below stack:

http-server for a lightweight serving of my static files

Rollup.js for «bundling»

Babel for transpiling (as I typically write in ES6)

React as a rendering engine

I initialized an npm project, installed and configured the tools, and created two react components:

A button to be rendered on the main page with all of the logic

A component with a form, to be displayed in the pop-out

I then used tutorials on React to:

Define a component link

Determine the state link

Create a components link for communicating among components

Here’s the main component of the starting source:

Note that I added a div element with a button, which opens a window with about:blank (it’s basically empty). This window returns an opened handle. To manipulate the window at will, I stored an internal reference to it. To determine if I could render something meaningful in that window from the parent, I added a function to render the PopOut form controller and updated the button click handler to use that rendering:

Here is the form component:

This component can handle input changes and render a simple form. It also exposes an event on FormSubmit to be used by the parent, as would be the case if both components resided on the same page. Here’s what it looks like:

Note that, miraculously, the address displays! Further, with no additional requests to the server, all of the rendering and business logic has already been downloaded and initialized and resides in the parent window. Still, the name of the window is not set (you can see about:blank in the address). After all, for security reasons, the address bar cannot be hidden in most browsers. So, I decided to add a dummyWindow.html to lend the feel of a real page and avoid the caveat of same origin policy breach. The page contents are:

​Realizing that this would result in a post-back and some downloads, I updated the handleClick to begin the rendering process after requests were successful:

Here’s the result:

The final flourishes

Next, I initialized a counter in the parent (along with an interval function) to check if the allocated memory would still remain after the parent closed. The result: after closing the parent, an orphan child does not get re-rendered, as there are no more triggers for it in the form.

To establish back-and-forth communication, wire the components so that logic for updating counters would reside in the child component. Verify this by entering the name into the form and clicking Save. You will see that the actual functionality of the PopOut does not end when it is orphaned. This means that if I bind the name state property to the display, it will get updated even if the parent is closed.

With this in mind, if creating a progress modal window for a long-running process, the initialization of that process plus hooking to the update should occur in the boundary of the child element.

Another logical conclusion: Since the parent is responsible for everything that happens in the PopOut, all console.log messages and debugging happen in the parent.

Improved functionality in less time

Altering the placement of logic truly delivers powerful results. In this case, my strategy simplifies Document Object Model (DOM) construction, manipulation, and access, reduces pop-up windows load times to none, unites pop-up window and main page. No more writing boilerplate javascript and creating separate pages for these purposes!