MWorks 0.13 is now available for Mac and iPad. Highlights of this release include:
MWorks 0.13 requires a Mac running macOS Monterey (12.0) or later or an iPad running iPadOS 17.0 or later. It was tested on macOS 12, 13, and 14 and iPadOS 17.
For a full list of changes in this release, please see the release notes below.
Added Optic Flow Field stimulus
Added exit actions. These can be used to perform work in a Task System State after a transition succeeds or to run unconditional shutdown or cleanup code (similar to Python’s try/finally or Swift’s defer).
Experiment media files are now sent one at a time from client to server. This eliminates the need for all media files to fit in RAM simultaneously, which was particularly problematic on iPad’s.
Variable notifications and announcement now happen atomically within assignments. This means that a variable’s attached actions cannot execute on more than one thread simultaneously (and therefore cannot interfere or overlap with actions executing on another thread).
Element assigments to variables now perform notifications and announce only if the assignment succeeds
Resolved an issue where client-side code lookups for experiment-defined variables would continue to succeed after the experiment was unloaded
Added support for analog waveform output to LabJack LJM devices
Added Rotary Speed Sensor device
QCUALOR device
Start IO Device now configures active channels only (more info)
Added log_commands parameter
Setting #allowAltFailover to false now actually works as intended
Attempting to make an I/O device its own “alt” object is now an error
Workspace files: Accept JSON5 on input. Sort keys and don’t escape slashes on output.
Fixed a potential crash on macOS 14.1
Python plugin now embeds Python 3.11 (instead of 3.10)
Python tools now require Python 3.8 or later
MATLAB tools now require MATLAB R2022a or later
MATLAB tools now support both arm64 (Apple silicon) and x86_64 (Intel) processors
Upgraded to new versions of many supporting libraries:
Added StateSystem::executeAction. Use a singleton State instance (the “end state”) to indicate that there are no more states to execute. ActionVariableNotification, ScheduledActions, and RenderActions now use StateSystem::executeAction to execute their associated actions. Wait, WaitForCondition, and StimulusDisplayAction no longer have special-case code to handle execution outside of the state system. Action::execute is now pure virtual and private.
State::next now tries to return its parent’s next state (instead of the parent itself), in order to avoid an unnecessary invocation of the parent’s action
Removed Action::setName and all calls to setName in State subclasses, because any name set that way is overwritten during experiment loading by ComponentRegistry::registerObject (either directly or via ComponentRegistry::registerNewObject)
Added ContainerAction. If, Else, IfElse, and While now derive from ContainerAction.
Renamed global variable currentState to announceCurrentState
Added Swift ClientPluginCoordinator and ClientPluginViewController classes to MWorksCocoa
Added ReadWriteVariable class. GlobalVariable and ScopedVariable now inherit from ReadWriteVariable
Use SQLite exclusive locking mode when reading MWK2 files
Removed OpenALContextManager, LegacySound and its subclasses, alut, and all usage of OpenAL
MWorks 0.12.2 is now available for Mac and iPad. This release includes the following changes:
active_when_hidden parameter to rectangular and circular fixation points, which can be used to restore their pre-0.12 behavior when off screenMWorks 0.12.2 requires a Mac running macOS Big Sur (11.0) or later or an iPad running iPadOS 16.0 or later. It was tested on macOS 11, 12, and 13 and iPadOS 16.
MWorks 0.12.1 is now available for Mac and iPad. This release fixes an issue in MWorks 0.12 that, in certain circumstances, caused audio playback to fail after unloading an experiment.
MWorks 0.12.1 requires a Mac running macOS Big Sur (11.0) or later or an iPad running iPadOS 16.0 or later. It was tested on macOS 11, 12, and 13 and iPadOS 16.
MWorks 0.12 is now available for Mac and iPad. Highlights of this release include:
MWorks 0.12 requires a Mac running macOS Big Sur (11.0) or later or an iPad running iPadOS 16.0 or later. It was tested on macOS 11, 12, and 13 and iPadOS 16.
For a full list of changes in this release, please see the release notes below.
MWorks’ support for audio stimuli has undergone a major overhaul and modernization:
Audio File Stimulus (formerly Sound Stimulus) now supports any audio file format readable by the operating system
Audio files can now be configured to loop indefinitely or repeat a fixed number of times
Added Tone Stimulus for generating simple tones
Audio stimuli now support dynamic changes to volume and stereo panning and can notify the experiment when they have ended
Play Sound now supports specifying a start time for playback, which enables synchronization of playback start with other sounds or events in the experiment
Audio stimuli can now be loaded and unloaded by a running experiment
Audio stimuli can now be placed in a Sound Group, which should make it easier to manage large sets of stimuli
For more information, see this discussion.
Added support for using multiple, independent stimulus displays in a single experiment (more info)
Fixation point stimuli (both rectangular and circular) now report active fixation only when on screen
Stimuli and display-related actions (e.g. Update Stimulus Display) can now specify the display with which they are associated (required when using multiple displays)
Exceptions raised during Load Stimulus execution no longer cause the experiment to stop or crash
Stimulus Display device now supports setting custom update and capture variables
On macOS, fixed a bug that prevented color management from being fully disabled
Added support for LabJack LJM devices (specifically the T4 and T7)
Added support for the University of Washington Quad Channel Laser Modulator (QCUALOR)
Added support for TRACKPixx3 eye trackers
DATAPixx devices are now compatible with the VPixx Device Server. An unfortunate consequence of this is that the MWorks’ DATAPixx interface now supports only x86_64 (Intel) processors. Support for arm64 (Apple silicon) processors will be re-added if/when the underlying libraries support it.
ISCAN devices now handle omission of the serial_port parameter correctly
Added display parameter to EyeLink, mouse input, and touch input devices (required when using multiple stimulus displays)
XIMEA camera now supports both arm64 (Apple silicon) and x86_64 (Intel) processors
Removed support for ITC-18 and NI-DAQ devices, because their vendor-provided drivers are incompatible with macOS 11 and later
Removed legacy MSSWGamepad plugin, as it crashed MWServer on recent macOS releases and is fully replaced by the USB HID device
Added support for conditional code inclusion
Added support for requiring macro definitions
%define x is now accepted as shorthand for %define x = true
Parser now waits to load included files until after the entire including file has been parsed
Expression parser functions refresh_rate, next_frame_time, and display_bounds now support non-default displays
Added support for component parameter name aliases
Experiment-defined variables and selection variables can now include descriptions (more info)
Improved run-time descriptions of system variables
Warnings and non-fatal errors are now silenced when evaluating expressions at load time
#mainScreenInfo is no longer required to contain the key refresh_rate_hz (which is currently unused)
Display-selection menu now shows localized display names (e.g. “Built-in Retina Display”, “LED Cinema Display”) instead of generic names (e.g. “Main display”, “Display 2”)
Mirror window location is now preserved between sessions
Eye calibrator window now supports preserving hidden parameters on update
Variables window now uses variable descriptions as tooltips for variable names
Python plugin now embeds Python 3.10 (instead of 3.9)
Python tools now require Python 3.7 or later
Added mwk2reader.py, which provides pure-Python tools for reading MWK2 files (more info)
Added get_version and require_version functions and __version__ attribute to Python mworks module (more info)
MATLAB tools now require MATLAB R2020b or later
Added MATLAB MWKFile class, which supports extracting events from an event file one at a time in order to avoid filling up system memory
Upgraded to new versions of many supporting libraries:
C++ code is now compiled using the C++20 language standard
The default C/C++ optimization level is now “3” (instead of “s”)
Moved most of Sound’s implementation into new LegacySound class. OpenALSound now derives from LegacySound.
Moved contents of StandardSounds.h and StandardSounds.cpp into corresponding LegacySounds.* files.
Added MWClientPluginViewControllerFactory protocol and MWClientPluginViewController class to MWorksCocoa
Client plugin window controllers can now subclass NSViewController (in addition to NSWindowController)
MWorksCocoa can now be imported as a module
MWorks 0.11 is now available for Mac and iPad. Highlights of this release include:
Please note: This is the last MWorks release that will support ITC-18 and NI-DAQ devices.
MWorks 0.11 requires a Mac running macOS Mojave (10.14.6) or later or an iPad running iPadOS 14.7 or later.
For a full list of changes in this release, please see the release notes below.
MWorks now provides native support for the arm64 (aka Apple silicon) processor architecture on macOS. All macOS applications, plugins, and tools now include native binaries for both arm64 and x86_64 (Intel) processors, except for the following components, which depend on Intel-only external libraries:
Native arm64 versions of these components will be added in a future release if/when arm64 versions of the required libraries become available.
All standard stimulus types have been reimplemented using Apple’s Metal API. Existing OpenGL-based stimuli are still supported and can be used alongside Metal-based stimuli, but this support will likely end in the next MWorks release.
The transition to Metal necessitated changes (mostly minor) to some stimulus types:
Blend factors can no longer be changed after the stimulus is loaded
Added max_num_dots parameter to moving dots
Added max_size_x and max_size_y parameters to text stimulus
The effects of some stimulus-related actions performed by render actions may not be visible until the next display update pass
Added support for stimulus display frame capture (more info)
Added Python image stimulus
Added central_starting_phase parameter to drifting grating
Normalized Gaussian mask values are now clamped to [0,1]. This fixes an issue where the mask could produce unintended colors when blending with a non-grayscale background. Applies to both the mask and drifting grating stimuli.
Fixed a rendering error that produced unintended edge effects in text stimulus
Attempts to create a video stimulus from an audio-only file are now handled properly
Image file stimulus no longer uses mipmaps, as they consume GPU resources and seem unlikely to offer any benefit in actual usage
The display update thread now gets a brief “warm up” interval before the experiment starts. This seems to eliminate the single “update_stimulus_display action took more than two display refresh cycles” warning often seen when an experiment starts on iOS.
Reduced lock contention between main state system thread and stimulus display update thread, which could lead to serious performance issues on iOS
Added support for XIMEA cameras (more info)
USB HID device now detects and reports device removal and can recover if the device is reconnected (more info)
Mouse input device parameters mouse_position_x and mouse_position_y are now optional, so that the device can be used just to hide the cursor
Ensure that clock offset is computed even when there are no input channels
Handle devices that don’t support pixel mode and/or VSYNC mode (e.g the original DATAPixx)
Stimulus display device parameter background_color is now optional
Replicators can now contain sounds
Added predicted_output_time parameter to clear stimulus display action
Update stimulus display action is now slightly more lenient when deciding if a display update has taken too long to complete
Fixed some issues in and improved the method of getting the server address on iOS
Addressed some UI issues on macOS 11 and 12
On iOS, don’t block the first-run dialog asking for permission to use the local network
Clarified MWServer’s “Use color management” preference
Python bridge window now alerts the user if the script fails to launch (e.g. because the selected Python executable doesn’t exist)
Variables window now permits selection of group headings
Variables window now discards input that contains only whitespace
Python plugin now embeds Python 3.9 (instead of 3.8)
Python tools now require Python 3.6 or later
Python conduits
Added CachingIPCClientConduit, which receives events for all codes and caches the most recent data for each (more info)
Added register_callback_for_all_events method
register_callback_for_code now actually works in all situations
MATLAB tools now require MATLAB R2018b or later
Upgraded to new versions of many supporting libraries:
StimulusDisplay, OpenGLContextManager, and their subclasses have been significantly reworked as part of the transition from OpenGL to Metal
Stimulus classes must now declare their required rendering mode by implementing (or inheriting) the method getRenderingMode
Removed support for OpenGL on iOS
Datum instances can now be marked non-compressible, which prevents MWK2Writer from trying to compress their serialized representation
All standard conduits (server, client, and Python) now use ZeroMQ for event transport (instead of shared-memory IPC)
The directories /Library/Application Support/MWorks/Developer/include and /Library/Application Support/MWorks/Developer/lib now contain architecture-specific subdirectories for arm64 and x86_64
MWorks 0.10 is now available for Mac and iPad. Highlights of this release include:
MWorks 0.10 requires a Mac running macOS High Sierra (10.13) or later or an iPad running iPadOS 13.7 or later.
For a full list of changes in this release, please see the release notes below.
Added render actions stimulus, which simplifies animation of other stimulus types
Most stimulus types now have blending parameters that allow detailed control over color and alpha blending
Added option to disable image load/unload messages
Blending is now handled correctly, even if the image file has an alpha channel
Movie and frame list stimuli with no frames now issue an error when starting to play
In previous releases, enabling redraw_on_every_refresh caused the stimulus display to continue updating even when the experiment was paused. This is no longer the case; display updates are now paused when the experiment is paused and resume when the experiment resumes.
Layer stimulus now renders in to a half-precision float, RGBA framebuffer texture. This resolves a potential, subtle blending issue on Mac’s with Intel graphics hardware.
Fixed an intermittent crash in video stimulus
MWorks now prevents the creation of two stimuli with the same name
Added DATAPixx device, which supports VIEWPixx displays and DATAPixx I/O hubs
Added face recognizer device, which captures images from a camera and uses a Core ML model to classify them
Added digital input pulse and digital output pulse channels. (Note that these rely on non-standard extensions of the Firmata protocol and require MWorks-specific firmware on the device.)
Now supports optional automatic reconnection
Now optionally reports the current connection state
Added stop action for stopping an active run before it completes
MWorks now stops the driver, terminating any active run, when Stop I/O Device executes or the experiment ends
Added temp_calc parameter
Added simulation mode
Removed undocumented, unused HIDPlugin (not to be confused with USB HID device, which is alive and well)
Added support for variable and expression interpolation in string literals
Added functions acos, asin, atan, atan2, date, and fmod
Modulus (%) operator now warns when truncating either of its operands
$varname and ${varname} are now accepted as variable names (and are equivalent to plain varname)
Added support for automatic, experiment-side data file management via the new data file device (more info)
When creating an event file, MWorks now prepends the standard data file path only if the user-provided filename is not itself an absolute path. This allows users to store event files in any directory, as long as they provide an absolute path as the filename (more info).
Resolved potentially severe reduction in data file write speed when system is under heavy I/O load
Removed #announceStimulus system variable, as its values were 100% redundant with #stimDisplayUpdate and served only to increase event file size
Task system state now forbids the placement of actions after transitions. (Previously, actions placed after transitions were silently moved to the end of the action list and always executed before transitions were evaluated.)
Wait for condition can now execute outside of the main state system (e.g. in a scheduled action)
MWEL now accepts $id (in addition to ${id}) as an identifier part
MWorks now prevents the creation of two variables with the same name
Removed MWEditor along with all related files and documentation. (Existing XML-based experiments remain fully supported, but new experiments should be written in MWEL.)
MWorks for iPad now supports Dark Mode
Added Image Viewer window, which enables viewing of images logged by a face recognizer
Python bridge window
Now requires the user to specify the Python executable to invoke (must be Python 3.5 or later)
Now sets the PYTHONPATH environment variable to /Library/Application Support/MWorks/Scripting/Python
Now truncates displayed script names at the beginning (instead of in the middle or at the end)
Now limits length of recent Python scripts list
Variables window now displays <binary data> in place of values that cannot be converted to text
All plugin windows now include the server address in their title
Added tooltips containing the entire, non-truncated paths of the experiment and data file
Saved variable set names are now sorted
Now limits length of recent servers list
Python plugin now embeds Python 3.8 (instead of 3.7)
Python plugin now supports ctypes on both Mac and iPad (although its usefulness on an iPad is very limited)
Python tools now support Python 3.5 and later, but no longer support Python 2
Python tools no longer require NumPy but still interoperate with it when available
Added _stop_main_loop method to Python conduit classes
Added context manager methods __enter__ and __exit__ to Python conduit classes; the former initializes the conduit, and the latter finalizes it
Added dump_codec and dump_events scripts to Python tools. They are installed in /Library/Application Support/MWorks/Scripting/Python.
MATLAB tools now require MATLAB R2017b or later
Upgraded to new versions of many supporting libraries:
Removed matlab-xunit from supporting libs
Removed all MWLibrary.xml files
Reworked build and installation to avoid the need to change permissions on system directories. Updated build instructions accordingly.
macOS installer package is now notarized
macOS and iOS builds now use separate code signing config files
C++ code is now compiled using the C++17 language standard
All Objective-C/Objective-C++ code now uses Automatic Reference Counting (ARC)
Added MWorksSwift framework, which aims to enable development of MWServer, MWClient, and client plugins in Swift (and Objective-C), without requiring any C++ code
Moved embedded Python out of PythonPlugin and in to the new MWorksPython framework (which PythonPlugin uses)
MWEL scripts now invoke a custom, private Python executable (which links against the MWorksPython framework)
Addressed issues raised by Python test suite on iOS
NumPy is no longer built against Accelerate, as it seems to make things worse rather than better
Replaced all usage of /bin/bash (and some usage of /bin/sh) with /bin/zsh
National Instruments (NI) recently announced that they are ending development of the NI-DAQmx Base device driver package. Given that the most recent version of NI-DAQmx Base (15.0) was released four years ago, this news is not especially surprising. However, it will affect anyone using NI devices with MWorks, as detailed below.
MWorks’ NIDAQ device uses NI-DAQmx Base to interface with NI hardware. NI has stated that the current (and final) version of NI-DAQmx Base will not be compatible with macOS Catalina (10.15), which is due to be released some time next month. Therefore, if you wish to continue using NI devices with MWorks, you will need to be running macOS 10.14 or earlier.
Extrapolating Apple’s recent cadence of macOS releases in to the future, we can expect macOS 10.16 to be released in the fall of 2020, with 10.17 following in the fall of 2021. At that point, Apple will end support for macOS 10.14, and MWorks will follow suit. Hence, the spring 2022 release of MWorks will require macOS 10.15 or later. Unless NI changes course and provides an updated or replacement driver package for macOS, MWorks’ support for NI devices will end with this release.
If you currently use NI hardware with MWorks and would like to continue to do so in the future, you may want to get in touch with the folks at NI and lobby for continued support of macOS. However, assuming that NI is unwilling to change its plans, you need to start considering alternative I/O hardware.
For control and simple data-acquisition tasks, I heartily recommend MWorks’ Firmata interface. Firmata-compatible devices (e.g. Arduino boards) are inexpensive, flexible, and ever-increasingly powerful. They are an excellent choice for controlling juice pumps, monitoring digital or analog triggers, and many other I/O tasks.
If you require more traditional DAQ hardware (for example, you need to record many analog channels simultaneously, or you require a sampling interval of less than one millisecond), I suggest that you consider LabJack devices. Several labs currently use the LabJack U6 with MWorks (via a custom plugin), and I’m planning to include built-in support for the T4 and T7 in the next MWorks release.
Finally, if you’d prefer to use I/O hardware from another vendor, please get in touch, and we can discuss options for interfacing with it from MWorks. In general, we should be able to support any device that comes with a macOS-compatible C/C++ API or communicates with the host computer via a platform-agnostic protocol (e.g. Ethernet or serial).
If you’re thinking about upgrading to macOS Mojave (10.14) (perhaps to take advantage of the new Dark Mode support in MWorks 0.9), here are a few things to consider first.
Update (2019/8/12): The issue described below appears to be fixed in macOS 10.14.6. I no longer observe the telltale stuttering on either of my Mojave systems. Reportedly, the issue is absent in the macOS Catalina beta as well.
macOS Mojave appears to have trouble driving multiple displays simultaneously. The issue manifests as visible stuttering in on-screen graphics. In MWorks, these stutters are accompanied by bouts of “Skipped xx display refresh cycles” messages. In my experience, the stuttering episodes occur cyclically, with 1-2 minutes of stuttering followed by 5-10 minutes of normal graphics performance. The only remedy is to reduce the total number of connected displays (both internal and external) to one.
I have observed this issue on a late-2013 Mac Pro and a 2018 Mac mini, both running macOS 10.14.4 (though it may affect earlier 10.14 releases, too). I have not observed it on earlier macOS versions. Also, this issue is not present on iOS.
Mojave is the first macOS release to require a graphics card that supports Metal, Apple’s modern graphics programming framework. Most Mac computers released since 2012 support Metal. However, the stock graphics cards in the 2010/2012 Mac Pro (i.e. the last “cheese grater” Mac Pro) do not.
Fortunately, you can make a 2010/2012 Mac Pro compatible with Mojave by upgrading its graphics card. Apple provides a list of supported graphics cards, any of which should be fine for use with MWorks. Even if you don’t plan to switch to Mojave any time soon, this upgrade may still be worthwhile as a future-proofing step. (I recently installed an MSI Gaming Radeon RX 560 128-bit 4GB GDRR5 in one of my MWorks test systems, a 2010 Mac Pro running macOS 10.13.6, and have been very happy with its performance.)
MWorks 0.9 is now available for macOS and iOS. Highlights of this release include:
MWorks 0.9 requires a Mac running macOS Sierra (10.12) or later or an iPad running iOS 12.2 or later.
For a full list of changes in this release, please see the release notes below.
Added xml2mwel script for converting XML experiment files into MWEL
Variable declarations are now a special case of component declaration and therefore can include parameters and/or children
Statement macro invocations can now include a default value with = (as long as the macro body is a single variable declaration that does not include a default value)
Added support for nestable, multiline comments delimited by /* and */
Parser now expands all enclosing macro parameters in children attached to macro invocations
Improved error reporting for unterminated string literals
mwel2xml now accepts --omit-metadata as a command-line option, which inhibits the inclusion of location info and experiment source in the generated XML
Movie and frame list stimuli can now have their frames attached as children (instead of being contained in a stimulus group)
Image file stimulus now prevents image color values from being altered when color management is disabled
Added rand_seed parameter
Added default values for field_center_x, field_center_y, and direction parameters
Stimulus display is now backed by Metal (always on iOS, and on Macs running macOS 10.13 or later that support Metal)
Added support for setting the stimulus display’s gamma function (only on macOS, and only if color management is disabled)
Added support for making the main stimulus display window non-opaque (mirror window is still always opaque)
Stimulus display is now created only if the experiment uses it
Update Stimulus Display action now issues a warning if it takes more than two display refresh cycles to complete
Dropped support for render_at_full_resolution key of #mainScreenInfo. Stimuli are now always rendered at the full, native resolution of the display.
Added word output and digital input pullup channels for Firmata devices
Added support for tracker-driven calibration
Enabled reporting of EyeLink blink, saccade, and fixation events
tracking_dist is now required only when eye_x, eye_y, and/or eye_z are specified
Error messages now include EyeLink error message (if available)
Improvements to analog output voltage channels
Added analog_output_enabled parameter
When stopping device, all digital output lines are now set to low, and all (non-waveform) analog output voltage channels are set to zero
Added workaround for bug in NI-DAQmx Base that manifests in 64-bit processes on macOS 10.12 and later
Now requires 64-bit variant of NI-DAQmx Base (i.e. version 14.0 or later)
New on-disk format for event files (MWK2)
Expression parser now supports multiplication of strings and lists by integers. Multiplying a list or string by integer n results in the concatenation of n copies of the list or string, e.g.
[1, 2, 3] * 2 == [1, 2, 3, 1, 2, 3]
3 * 'abc' == 'abcabcabc'
New app icons
Version info for all apps now includes the build date
MWClient and MWServer now support Dark Mode
macOS installer now backs up existing MWorks installation silently (without popping up a dialog box)
MWServer and MWClient now preserve the location of their preferences windows between sessions
iOS MWorks app now supports hiding the “Choose experiment” button
New user interface icons
Eliminated some spurious connection failures
Calibrator and reward window’s action buttons now end editing in all fields (thereby committing any pending changes) before performing their task
Eye window now presents its options in a panel (instead of a drawer)
Added code to prevent App Nap from delaying response to client connection requests
Now preserves the selected preferences window tab between sessions
Python and MATLAB data tools now transparently support both MWK and MWK2 files
Python plugin is now available on iOS. Includes all features available on macOS (run file and run string actions, Python file resources, and the expression parser functions py_eval and py_call).
Functions message, warning, and error are now available to code executed by the Python plugin
Python plugin now embeds Python 3.7 (instead of 2.7). In addition, the plugin now includes its own copies of Python and NumPy (no external Python installation required).
Removed MWKStream class from Python data tools
Python tools now support Python 2.7 and 3.7. (Python 3.6 is no longer supported.)
MATLAB tools now require MATLAB R2016b or later
Added iOS installation and configuration instructions
Updated Running an Experiment to cover launching and connecting to MWorks on iOS
Added iOS version of FindTheCircle example
Analyzing Experimental Data now explains how to access event files stored on iOS
Added descriptions of current and legacy event file formats
Added documentation on the Python mworkscore module and the execution environment of embedded Python code (see Run Python File)
Other minor improvements
Upgraded to new versions of several supporting libraries:
Added OpenSSL 1.1.1b, Python 3.7.3, NumPy 1.16.2, and SQLite 3.27.2 to supporting libs
All code is now compiled using the C++14 and C11 language standards
Added support for stimuli with child components
BasicTransformStimulus now enables blending when drawing; subclasses can override the blend equation
Added new MacOSOpenGLContextManager (used only on systems running macOS 10.13 or later that support Metal). Old MacOSOpenGLContextManager is now called LegacyMacOSOpenGLContextManager.
IOSOpenGLContextManager, MacOSOpenGLContextManager, and LegacyMacOSOpenGLContextManager are now private to MWorksCore. Plugins that need access to platform-specific resources should use AppleOpenGLContextManager.
MWorks for iOS is now available on the App Store.
MWorks’ iOS app is a port of MWServer to the iOS platform. It supports nearly all of the component types available on macOS. (The only exceptions are some I/O devices and Python actions and resources, though the latter may be added in a subsequent release.) The app can load and run MWorks experiments stored locally or in the cloud, or you can connect to and control it from MWClient on a Mac.
The current release (version 0.8.1) requires an iPad running iOS 11.4 or later. It is compatible with MWorks 0.8 on macOS.
For more information, visit the iOS app section in the knowledge base. If you have any questions, please contact us.