With an all-new design that looks great on macOS Big Sur, Xcode 12 has customizable font sizes for the navigator, streamlined code completion, and new document tabs. Xcode 12 builds Universal apps by default to support Mac with Apple Silicon, often without changing a single line of code.
Designed for macOS Big Sur.
Download Slack for free for mobile devices and desktop. Keep up with the conversation with our apps for iOS, Android, Mac, Windows and Linux.
Name OS Size Last Update; Yamaha Steinberg USB Driver V2.0.4 for Mac macOS 10.15-10.12: Mac: 3.4MB: 2020-11-25: MONTAGE Connect V1.1.1 for Windows: Win: 17.2MB. Download Slack for free for mobile devices and desktop. Keep up with the conversation with our apps for iOS, Android, Mac, Windows and Linux. Besides that, when it comes to Safari, Mac search engine, there are some notable improvements with the update. The users can now control annoying auto-play videos, prevent tracking, and more. There are also notification controls, and you will experience a boost in performance, too. The most noticeable changes took place in Apple’s Photo App. Global Nav Open Menu Global Nav Close Menu; Apple; Shopping Bag +.
Xcode 12 looks great on macOS Big Sur, with a navigator sidebar that goes to the top of the window and clear new toolbar buttons. The navigator defaults to a larger font that’s easier to read, while giving you multiple size choices. New document tabs make it easy to create a working set of files within your workspace.
Document tabs.
The new tab model lets you open a new tab with a double-click, or track the selected file as you click around the navigator. You can re-arrange the document tabs to create a working set of files for your current task, and configure how content is shown within each tab. The navigator tracks the open files within your tabs using strong selection.
Navigator font sizes.
The navigator now tracks the system setting for “Sidebar icon size” used in Finder and Mail. You can also choose a unique font size just for Xcode within Preferences, including the traditional dense information presentation, and up to large fonts and icon targets.
Code completion streamlined.
A new completion UI presents only the information you need, taking up less screen space as you type. And completions are presented much faster, so you can keep coding at maximum speed.
Redesigned organizer.
An all-new design groups all critical information about each of your apps together in one place. Choose any app from any of your teams, then quickly navigate to inspect crash logs, energy reports, and performance metrics, such as battery consumption and launch time of your apps when used by customers.
SwiftUI
SwiftUI offers new features, improved performance, and the power to do even more, all while maintaining a stable API that makes it easy to bring your existing SwiftUI code forward into Xcode 12. A brand new life cycle management API for apps built with SwiftUI lets you write your entire app in SwiftUI and share even more code across all Apple platforms. And a new widget platform built on SwiftUI lets you build widgets that work great on iPad, iPhone, and Mac. Your SwiftUI views can now be shared with other developers, and appear as first-class controls in the Xcode library. And your existing SwiftUI code continues to work, while providing faster performance, better diagnostics, and access to new controls.
Universal app ready.
Xcode 12 is built as a Universal app that runs 100% natively on Intel-based CPUs and Apple Silicon for great performance and a snappy interface.* It also includes a unified macOS SDK that includes all the frameworks, compilers, debuggers, and other tools you need to build apps that run natively on Apple Silicon and the Intel x86_64 CPU.
Updated automatically
When you open your project in Xcode 12, your app is automatically updated to produce release builds and archives as Universal apps. When you build your app, Xcode produces one binary “slice” for Apple Silicon and one for the Intel x86_64 CPU, then wraps them together as a single app bundle to share or submit to the Mac App Store. You can test this at any time by selecting “Any Mac” as the target in the toolbar.
Test multiple architectures.
On the new Mac with Apple Silicon, you can run and debug apps running on either the native architecture or on Intel virtualization by selecting “My Mac (Rosetta)” in the toolbar.
Multiplatform template
New multiplatform app templates set up new projects to easily share code among iOS, iPadOS, and macOS using SwiftUI and the new lifecycle APIs. The project structure encourages sharing code across all platforms, while creating special custom experiences for each platform where it makes sense for your app.
Improved auto-indentation
Swift code is auto-formatted as you type to make common Swift code patterns look much better, including special support for the “guard” command.
StoreKit testing
New tools in Xcode let you create StoreKit files that describe the various subscription and in-app purchase products your app can offer, and create test scenarios to make sure everything works great for your customers — all locally testable on your Mac.
Get started.
Download Xcode 12 and use these resources to build apps for all Apple platforms.
Plexon Online Software Download Mac Software
Installation > Apparatus > Plexon Interface ModulePurpose: Merging Maestro and Plexon MAP data streamsIn late 2003 our laboratory purchased the first of several Plexon™ Multichannel Acquisition Processors. The Plexon gives us the ability to record the signals from an array of extracellular electrodes and from these signals isolate one or more neural 'units' in real time. While Maestro and the Plexon operate independently, it was important to design some mechanism by which online or offline analysis software could merge their data streams, i.e., synchronize their separate data acquisition timelines. The Plexon is capable of timestamping character data on an 8-bit 'strobed digital word' input port as well as pulses received on 8 individual TTL 'event inputs'; both the 8-bit port and the event inputs are accessible on a 26-pin front-panel digital input connector. In addition, the Plexon has two higher-accuracy TTL inputs (25µs pulse width minimum, instead of 250µs). Given these resources, we decided that the simplest way to integrate the two acquisition systems was to have Maestro send both character data and marker pulses to mark key events during Trial and Continuous mode; these can be read in and timestamped by the Plexon.Reserved ASCII codes for Maestro-Plexon integration- 0x2 ('start'): Trial started, or recording started in Continuous mode.
- 0x3 ('stop'): Trial ended, or recording stopped in Continuous mode.
- 0x5 ('rewardDelivered'): Reward delivered to subject. Immediately followed by reward pulse length in milliseconds, as a null-terminated string.
- 0x6 ('dataSaved'): Data file was successfully saved.
- 0x7 ('noFile'): Serves as a placeholder for data file name in Trial mode when no file is to be saved. Followed by a null character.
- 0xE ('lostFix'): Trial aborted because subject lost fixation.
- 0xF ('abort'): Trial aborted for a reason other than lost fixation. In Continuous mode, recording aborted for some reason.
In Trial mode, several ASCII character codes and other character strings are sent before and after a trial. All character data written during a single trial are always bracketed by the 'start' (ASCII 02h) and 'stop' (ASCII 03h) character codes. The 'start' code is immediately followed by the null-terminated name of the trial, then the null-terminated data file name. The latter is particularly important so that an analysis program can properly merge the Plexon unit data with the behavioral responses recorded by Maestro. However, if the trial is not to be saved in the first place, a 'noFile' (ASCII 07h) character code, followed by a null character (ASCII 00h), serves as a placeholder for the data file name. After the trial has ended, if the animal lost fixation, a 'lostFix' (ASCII 0Eh) code is sent. If the trial aborted for any reason other than a fixation break, the 'abort' (ASCII 0Fh) character is written. If the data file was saved successfully, the 'dataSaved' (ASCII 06h) character is sent. Finally, the 'stop' code is then sent to mark the end of character data for the trial. A similar sequence of character data brackets the recording of a data file in Continuous mode. Before recording commences, the 'start' character code is sent, followed by the null-terminated data file name. If the recording aborts prematurely for whatever reason, the 'abort' character is sent (the data file is always discarded when recording is aborted in Continuous mode). Otherwise, if the data file is saved successfully, the 'dataSaved' code is written. Finally, the 'stop' character is always written to mark the end of the recording. In both Trial and Continuous modes, several characters are written each time a reward is delivered to the animal: a 'rewardDelivered' character code (ASCII 05h), followed by the nominal reward pulse length in milliseconds as a null-terminated string. This character sequence is sent after the reward is delivered. Note that, for the end-of-trial reward, the 'rewardDelivered' character sequence will be sent prior to the 'lostFix'/'abort', 'dataSaved', and 'stop' codes.
One could use the timestamps for the 'stop' and 'start' character codes to help align the Plexon and Maestro acquisition timelines during each Trial- or Continuous-mode recording. However, the accuracy with which the Plexon can timestamp the arrival of these character codes is poor, and there could be some variable delay in the delivery of a character. Thus, the character data only serves to provide information about what Maestro is doing. For synchronization purposes, Maestro dedicates the marker pulse on DO<11>; that pulse is routed to the high-accuracy XS1 or XS2 TTL input (25µs pulse width) on the Plexon's digital input module. In Trial mode, DO<11> is strobed immediately after the trial starts and immediately after the trial ends (even before the end-of-trial reward is delivered). In Continuous mode, DO<11> is strobed immediately after recording begins and then again just before it ends.
Keep in mind that Maestro is simply providing synchronization pulses, data file names, and other protocol information for recording in the Plexon data file. Analysis software must parse the Plexon file for this information and locate and digest corresponding Maestro data files in order to match Maestro-recorded behavioral data with Plexon-recorded unit data. Our lab has developed and maintained a Matlab tool for doing just that; consult the Data Analysis chapter for details.
Interfacing with the Omniplex DMaestro's Plexon interface module was originally designed for the Plexon MAP system back in 2003-4. The MAP system has since been replaced by a newer model, the Omniplex D. The digital input ports are different on the Omniplex, but it is still possible to connect it to the existing interface module via a special connector provided by the manufacturer -- the OPX DI MAP Mode 2 Emulator. You'll find a technical description of this connector in the 'Miscellaneous Documentation' folder on the Downloads page. The Plexon interface module is a custom hardware component that was designed to stream character data and deliver synchronization pulses to the Plexon. It plugs into the digital IO rack in the experiment rig and sits on the DIO event timer's digital output bus. For the synchronization pulses, it includes a modified version of the standalone marker pulse module that accommodates the Plexon's minimum pulse width requirements. A second device sends 8-bit ASCII character sequences to Plexon using a simple 'transmit-and-wait-for-not-busy' handshake protocol.
Modified Marker PulseDevice (device address DO<15..12> = 0001). The standard “marker pulse” device is just a simple latchfor the 12 possible data lines, DO<11..0>. Maestrowrites to the device to raise and then lower the TTL level on a digital output channel,thereby generating a short pulse.Theproblem is that these pulses are on the order of 1-3μs.The Plexon’s 8 general-purpose TTL “event”inputs require a minimum 250μs pulse width, while its high-accuracy inputs ( XS1 and XS2) require a 25μs pulse.To address this problem, the “modified” marker pulse device introduces one-shot timers and associated logic to essentially 'extend' the pulses to satisfy the Plexon's specifications (of course, the implicit assumption here is that Maestro does not need to deliver pulses to the Plexon more often than every 250μs or so). DO<8..1> arerouted to the Plexon’s 8 general-purpose TTL event inputs; pulses on these channels will meet the 250μs requirement. DO<11..9> are routed to BNC front-panel connectors on the plug-in module, labelled XS2..XS0, respectively; pulses on these three channels meet the 25μs requirement. Character Writer Device (device address DO<15..12> = 0111). Each time Maestrowrites to this device, it stores the 8-bit ASCII character DO<7..0> into an internalFIFO.On the output side, whenever theFIFO is not empty, the device pops the next character off the FIFO, stores itin a separate output latch that drives the Plexon’s 8-bit “strobed word” inputport, then handshakes with the Plexon by setting the INPSTRB line and thenwaiting for INPBSY to reset before writing the next character.The Plexon’s 8-bit input port requires aminimum interval of 150μs between strobe pulses (the strobe pulse itself musthave a width >= 0.25 μs) withouthandshaking, but faster updates are possible with handshaking. Maestrowill write the characters much faster than that (~1-3 μs) -- so the FIFO is essential. The logic must be able to simultaneouslywrite to Plexon while receiving new “characters” from Maestro. In addition to the 3 BNC outputs, the plug-in module includes a 26-pin flat ribbon cable connector on its front panel. The connector's pin-out matches the Plexon's digital input connector in Mode 2 (8 TTL event inputs plus an 8-bit strobed word): Pin
| Use | 1, 2, 19, 21
| Digital GND
| | 26 | +5V | 23, 25
| Not connected
| | 20 | INPSTRB | | 22 | RSTART | | 24 | INPBSY | 3 thru 10
| TTL EVENT3 (pulse on DO1) thru EVENT 10 (pulse on DO8)
| 11 thru 18
| 8-bit 'strobed' word input (maps to DO0..DO7)
|
|
|