If you're using PowerPoint for Microsoft 365 you have the option to let your slides be updated by your team even as you're presenting so that you always have the up-to-the-minute changes.
Traditionally once you've started your presentation your slides wouldn't update.
If you're working with a team of people to create your slide deck it may be that changes are being made to the slides right up to the last minute. On the Slide Show tab of the ribbon, clear the check box named Use Presenter View. If you want Presenter view turned off while you are showing your presentation to others: Tip: If you don't need to see the current slide in Presenter View at all, and would like your notes to be larger, drag that vertical separator line all the way to the left. What the notes look like in Presenter view To manually determine which screen shows your notes in Presenter view and which shows only the slides themselves, on the task bar at the top of Presenter view, select Display Settings, and then select Swap Presenter View and Slide Show. Swap the Presenter view and Slide view monitors See Using a laser pointer on your smartphone when presenting in PowerPoint for more information, including a brief video. You can use PowerPoint on your smartphone as a remote control to run your presentation and view your speaker notes. To hide or unhide the current slide in your presentation, select Black or unblack slide show. Press the Esc key when you want to turn off the pen, laser pointer, or highlighter. To point to or write on your slides as you present, select Pen and laser pointer tools. To view a detail in your slide up close, select Zoom into slide, and then point to the part you want to see.įor more details on zooming in, see Zoom in to part of a slide. I only use this operator sparingly, but in the case of in-line ad-hoc FsCheck Arbitraries, I find it useful.Īddendum : You can get rid of the nc value with TIE fighter infix notation.Tip: You’ll see thumbnails of all the slides in your presentation (as shown below), making it easy to jump to a specific slide in the show. When the last argument passed to a function is another function, you can replace the brackets with a single application of the <| operator. Notice that there's no longer any need for a closing bracket after Dead =! actual. The solution started to dawn on me because I've been learning Haskell for the last half year, and in Haskell, you often use the $ operator to get rid of unwanted brackets. To make a long story short, enclosing a multi-line anonymous function in brackets is a source of errors. None of the alternatives compile at this point.
Arraysync slide show code#
The editor doesn't have a chance, though, because at this point, I'm still typing, and the code doesn't compile. What it really should have done was this: There's already a closing bracket immediately to the right of the cursor, and the editor assumes that this bracket belongs to the opening bracket I just typed. What normally happens when you type an opening bracket is that the editor automatically inserts a closing bracket to the right of your cursor, but in this case, it doesn't do that. The editor detects that I'm writing an opening bracket, but since I have the closing bracket to the immediate right of the cursor, this is what happens: When I wrote the above property, for example, when I reached the point where I wanted to call the calculateNextState function, I wrote: If you ever need to use a nested level of brackets within that anonymous function, your vigilance will be tested to its utmost. When entering new lines, you have to keep diligent, making sure that the closing bracket is always to the right of your cursor. After you've typed the closing bracket, you have to move your cursor one place to the left. When you're writing the property, however, this syntax is cumbersome.Īfter having written Prop.forAll nc, you start writing (fun neighborCount -> ). While it isn't pretty, I haven't found it that bad for readability, either.
Notice how the opening bracket appears to the left of the fun keyword, while the closing bracket appears eleven lines down, after the end of the expression Dead =! actual. There's one tiny problem with this way of expressing properties using Prop.forAll: the use of brackets to demarcate the anonymous multi-line function. forAll nc ( fun neighborCount -> let liveNeighbors =ĬalculateNextState (cell :: liveNeighbors |> shuffle |> set) cell
Arraysync slide show how to#
Last year, I described how to define and use ad-hoc, in-line Arbitraries with FsCheck.Xunit. Slightly improved syntax for defining ad-hoc, in-line Arbitraries for FsCheck.Xunit.