Records on recovery after cholecystectomy of patients in a suburban Pennsylvania hospital between 1972 and 1981 were examined to determine whether assignment to a room with a window view of a natural setting might have restorative influences. Twenty-three surgical patients assigned to rooms with windows looking out on a natural scene had shorter postoperative hospital stays, received fewer negative evaluative comments in nurses' notes, and took fewer potent analgesics than 23 matched patients in similar rooms with windows facing a brick building wall.
At first I liked the answer given by @Asperi, but when trying it in my own environment I found it difficult to get working due to my need to know the root view at the time I create the window (hence I don't know the window at the time I create the root view). So I followed his example, but instead of an environment value I chose to use an environment object. This has much the same effect, but was easier for me to get working. The following is the code that I use. Note that I have created a generic class that creates an NSWindowController given a SwiftUI view. (Note that the userDefaultsManager is another object that I need in most of the windows in my application. But I think if you remove that line plus the appDelegate line you would end up with a solution that would work pretty much anywhere.)
It's not quite as clean as I would like it to be (I would prefer to have a solution where I did just say self.rootWindow?.close() instead of requiring the wrapper class), but it isn't bad and it allows me to create the rootView object before I create the window.
My camera is a Sony Nex3, and for this sort of thing I usually use it with an elderly Pentax-M 1:2.8 / 28mm manual focus lens with an adaptor, although I would be prepared to buy another (cheap manual!) lens.
Any camera is going to struggle with the dynamic range of that sort of situation. Very hard to get the room and the outside both exposed reasonably at the same time. With enough flash power you can do it by flooding the room with light I suppose.
Long exposure with multiple manual flash washing. Takes some experience but you can differentially illuminate target area. I have never done this "in anger" with a flash but using an LED or other lamp to "wash" an area at night with long exposure can be great fun and even useful.
Photo: With and without fill flash. I had minimal time to 'play', so no effort made to optimise, and it uses on-camera flash. Given time I'd reduce flash level somewhat and better balance ambient and flash so some shadowing remains from eg phone on bed or grand old lady [tm]. [Note full flash reflection in window of room opposite - whoops.]
Set your flash to AUTO or FILL. Move to a position where the flash will not reflect (from a window, mirror, hanging photo, or any other reflective surface) directly back at the camera. Take the shot.
I have used this method on both DSLRs and Point & Shoots (with MANUAL MODE ability). While I have gotten very good results using JPEG files out of the camera, the best ways to deal with this type of photo is to shoot it in RAW where you have much greater post editing ability.
Float: The tool window is detached from the tool window bar, floating on top of the main window. It is visible only together with the main project window. You can move it to a different monitor or desktop if necessary.
I could be in the minority, but split view is one of the best features of all time in Slack for me (productivity, sensory and monitoring wise). If you aren't familiar with the feature or are confused on the feature I am referring to, I am providing an screenshot here that was provided to me by Slack support (I redacted their information).
Split view let you have a thread open and it would persist as a side bar when navigating away from the channel the thread was located within. Now if you click on anything outside of the channel that you currently have a thread open in, the thread will close.
The new feature, windows in my opinion is clunky, far away from the original window and inferior to split view. I get bothered by notifications easily so I like to have a thread up to monitor while navigating into other channels and seeing other discussions.
Click and drag on the corner with the grabber (same one for making a new window) and drag DIRECTLY over the neighboring panel that you want to make disappear (if you drag anywhere else, you'll make a new panel). This will make a grey arrow which shows you which panel will get put on top of the other. Release the mouse button when your cursor is over the panel you want to go away.
Now, using this knowledge, you have a bit of a puzzle to solve. You have to close each of the windows in the red square individually. So I'd start with the smallest one first. Join it with the one with which it shares a complete edge, and the go to the next-smallest.
I felt the need to post another answer here, because so many of these answers appear to refer to old versions of Blender, or just are not clear, and I spent a good half hour at least just trying to figure out basic window management, pulling my hair out.
Like a lot off commenters on @Matt's top answer, I was really struggling to figure out why sometimes I was splitting the window and sometimes joining two windows. My mistake was that I was starting my drag exactly at the intersections of the windows.
If you start with the crosshair exactly on the boundary, then it's a lot more difficult to know which of the two operations you are going to end up doing, so be conscious about trying to grab a little bit inside the window that you want to split, or in the case of merging, start your drag within the one that you want to keep, out of a pair of adjacent windows.
Use a different app on one side: Click the app window, move the pointer over the green button in the top-left corner, choose Replace Tiled Window, then click the window you want to use instead. If you decide not to replace the current window, click the desktop to return to it.
Move an app window to the desktop: Click the app window, move the pointer over the green button in the top-left corner of the window, then choose Move Window to Desktop. The app is displayed on the desktop.
The app that remained in Split View is now full screen in its own space; to return to it, press Control-Up Arrow (or swipe up with three or four fingers) to enter Mission Control, then click the app in the Spaces bar.
I would look at a program like Divvy on the Mac App Store for customizing a workspace with multiple tiled windows. It's not split view, but it's far more flexible and able to make use of the 27 inch display space to quite a granular basis.
After downloading, installing, and granting the app accessibility permissions in System Preferences, you'll be able to enable the default keyboard shortcut scheme, which allows you to press ctrl + opt + U/I/K/J to snap a window to the top left/top right/bottom right/bottom left, respectively. By assigning four windows each to one of these four positions, you can create a four-way split screen view (and if you enable Dock and Menu Bar hiding, you might be able to get a bit more screen real estate, if needed).
yabai is a window management utility that is designed to work as an extension to the built-in window manager of macOS. yabai allows you to control your windows, spaces and displays freely using an intuitive command line interface and optionally set user-defined keyboard shortcuts using skhd and other third-party software.
Hopefully something like this becomes a standard Mac feature. I like the split screen feature, but sometimes I want/need more than two screens. I found a pretty good solution on the Apps store that will let you have split screen, one window half/two in quarters, or 4 windows is quarters. It is called Magnet. Works great on OSx Sierra, and is much cheaper than Divvy. Here's the link!
The app I am now using is Magnet. It is available on the Mac AppStore and performs beautifully. It has shortcuts, graphical buttons and you can drag the windows to the sides of the screen to snap them to halves or to corners to snap them to quarters.
BetterSnapTool allows you to easily manage your window positions and sizes by either dragging them to one of your screens corners or to the top, left or right side of your screen. This lets you easily maximize your windows or position them side by side. In addition, you can set keyboard shortcuts in order to move and resize your windows the way you want.
New with Windows 10 seems to be the Notification Area. Now, I've seen a few notifications (in the Action Center). The problem is that I haven't understood any of them (actively using computers for 30 years now), and once I click them they are gone. Is there any way to view these past user notifications so I can try and make some sense out of them?
The action center is the same as found on the Microsoft Phones running Windows 10 Mobile. These actions (notifications) are meant to be displayed to the user until they take action. There are two ways a user can interact with an action:
I've found one way to view past notifications, though only very recent ones. In Windows 10, the notifications are stored in \Users\\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db as an SQLite database. E.g. using DB Browser for SQLite, it is possible to view the "Notification" table in it, whose "Payload" column contains the notification texts.
Now, this database doesn't actually seem to store notification history, and dismissed notifications are immediately deleted, but there is a trick: since it is an SQLite database with write-ahead logging (WAL), it may be possible to view an earlier version of the database with the relevant notification.
For example, say I accidentally dismissed a notification without being able to read it. In the aforementioned directory, there exists wpndatabase.db file, last modified two hours ago, and wpndatabase.db-wal file, last modified just now. If I copy both files to a different directory and then open wpndatabase.db in DB Browser for SQLite, I will view the latest version of the database, with the relevant notification gone. However, if I copy only the wpndatabase.db file and open it, I will view the snapshot from two hours ago, before I dismissed the notification, so I will be able to view it.
0aad45d008