Skip to content

Client file locations

See also: Server file locations.

MultiTaction Canvus client organizes files across multiple folders. The files can be categorized as follows:

  • Configuration file: Canvus client configuration file is called mt-canvus.ini. There is an example and a working version of this file on your client machine.
  • Log files: Canvus client generates a log file while it is running.
  • Data files: Canvus client stores data files for your local canvases.
  • License files: Canvus client requires a license file.
  • Application files: Canvus client application itself.
  • Screen configuration file: Canvus requires a screen.xml file which specifies how content is rendered on the operating system desktop.
  • Input configuration file: Canvus requires a config.txt file which specifies how input from touchscreens is mapped on the application content.

Configuration file

The configuration file for Canvus client is called mt-canvus.ini. The Canvus client installation comes with an example configuration file that can be used as a reference.

Canvus reads the first working version it finds, in the order below, and ignores the other. The files are not combined, so a per-user file hides every setting in the system-wide file for that user. On Ubuntu the package creates the system-wide file on a fresh install. See Which file Canvus reads.

Where is mt-canvus.ini on Windows computers?

  • Working version:

    Canvus client automatically searches the following locations in order:

    1. %APPDATA%\MultiTaction\canvus\mt-canvus.ini
    2. %PROGRAMDATA%\MultiTaction\canvus\mt-canvus.ini

    Where %APPDATA% refers to the user profile of the user running Canvus client.

  • Example version: C:\Program Files\MT Canvus\Examples\mt-canvus.ini

Where is mt-canvus.ini on Ubuntu computers?

  • Working version:

    Canvus client automatically searches the following locations in order:

    1. ~/MultiTaction/canvus/mt-canvus.ini
    2. /etc/MultiTaction/canvus/mt-canvus.ini

    Where ~/ refers to the home folder of the user running Canvus client.

  • Example version: /opt/mt-canvus-<version>/Examples/mt-canvus.ini

Where is mt-canvus.ini on macOS computers?

  • Working version:

    Canvus client automatically searches the following locations in order:

    1. ~/Library/MultiTaction/canvus/mt-canvus.ini
    2. /etc/MultiTaction/canvus/mt-canvus.ini

    Where ~/ refers to the home folder of the user running Canvus client, and Library is the one inside that home folder (Finder hides it by default; reach it with Go → Go to Folder and paste the path).

The configuration file is not beside the logs

On macOS the configuration lives under ~/Library/MultiTaction/canvus/, while the log files are written to ~/MultiTaction/canvus/logs/. The two directories are deliberately different: Canvus stores per-user application data in the standard macOS location, and the launch wrapper writes its console log next to the other MultiTaction runtime folders. Putting mt-canvus.ini in the logs folder has no effect, because Canvus never reads it from there.

  • Example version: /Applications/MT Canvus.app/Contents/Resources/lib/Examples/mt-canvus.ini

    To start from the shipped examples, copy them out of the application bundle:

    mkdir -p ~/Library/MultiTaction/canvus
    cp -R "/Applications/MT Canvus.app/Contents/Resources/lib/Examples/"* ~/Library/MultiTaction/canvus/
    

Never edit files inside the application bundle on macOS

Editing anything inside MT Canvus.app breaks the code signature, after which macOS refuses to open the application. Always copy the example out to ~/Library/MultiTaction/canvus/ and edit it there.

Where is my data?

Canvus client stores data files for local canvases in the data-300 subfolder of the data folder. You set the data folder with content/root in the configuration file. The default location depends on the operating system:

  • Windows: %APPDATA%\MultiTaction\canvus-data\data-300
  • Ubuntu: ~/MultiTaction/canvus-data/data-300
  • macOS: ~/Library/MultiTaction/canvus-data/data-300

The data-300 folder holds, among other things:

  • asset-storage: the files on local canvases, and the files of shared canvases downloaded from Canvus Server. Allow disk space for it on clients that open large shared canvases. You can move it to another disk with identity/asset-directory; see Asset folder.
  • Canvus-folder: the built-in Canvus folder that the finger menu opens in multi-user mode.
  • Shortcuts: predefined text snippets, if you created them (see Predefined text snippets).
  • site-id: a file with an identifier that Canvus creates the first time it starts. It identifies this installation to Canvus Server.

Roaming profiles on Windows

On Windows the default data folder is in %APPDATA%, which is part of a roaming user profile. On sites with roaming profiles or virtual desktops, set content/root to a folder on a local disk.

Downloaded files

Files that users download from a canvas are saved to:

  • in single-user mode, and for guest users: the Canvus subfolder of the user's Downloads folder;
  • otherwise: userdata/<server>/<user id>/downloads inside the data folder.

Other per-user folders

Folder Windows Ubuntu macOS
Accepted server certificates and extra CA certificates (certificates/certificate-dir) %APPDATA%\MultiTaction\canvus\ca-certificates ~/MultiTaction/canvus/ca-certificates ~/Library/MultiTaction/canvus/ca-certificates
Automatic update backups and backups made with --backup (backup/root) %LOCALAPPDATA%\MultiTaction\canvus\backups ~/MultiTaction/canvus/backups ~/MultiTaction/canvus/backups

Where are the log files?

Canvus client writes a timestamped log file each time it starts. The exact file name depends on the platform and how the client is launched:

  • Windows, started from the desktop shortcut: mt-canvus-<date>.log.
  • Windows, started with mt-canvus.bat: log_<date>_<time>_<n>.log.
  • Ubuntu, started from the applications menu: log<timestamp>-.txt, plus mt-canvus-daemon-log<timestamp>-.txt for the helper process mt-canvus-daemon.

Find these log files in the following folders:

  • Windows: %LOCALAPPDATA%\MultiTaction\canvus\logs
  • Ubuntu: ~/MultiTaction/canvus/logs/
  • macOS: ~/MultiTaction/canvus/logs/

Additional console log on macOS

On macOS the same folder also holds mt-canvus-macos.log. This captures console output, including anything that fails before the application's own trace file is opened. When an application is launched from Finder there is no console, so this is the first file to check if Canvus does not appear at all.

Note

On Ubuntu and macOS, the log file is written by the launcher (the desktop entry or launch wrapper), not by the client itself. If you run mt-canvus-app directly instead of using the normal launcher, no log file is written on those platforms.

Note

On Windows, the installer configures Windows Error Reporting to keep up to 10 crash dumps of mt-canvus-app.exe in %LOCALAPPDATA%\CrashDumps.

Note

If Canvus client is started from Launcher, log entries are written to a pipeline log file. You can find pipeline log files here:

  • Windows computers: %LOCALAPPDATA%\MultiTaction\launcher\logs
  • Ubuntu computers: ~/MultiTaction/launcher/logs
  • macOS computers: ~/MultiTaction/launcher/logs

Where is the MT Launcher configuration?

On Windows, the installer writes the MT Launcher configuration for Canvus to %PROGRAMDATA%\MultiTaction\launcher\apps\mt-canvus-<version>.ini. See MT Launcher configuration.

Where is my client license?

The location for an activated Canvus client license depends on the operating system:

  • Windows: Canvus client searches these folders for a license, in order:
    • %PROGRAMDATA%\MultiTaction\Licenses
    • %LOCALAPPDATA%\MultiTaction\Licenses
    • %APPDATA%\MultiTouch\Licenses
  • Ubuntu: Canvus client searches these folders for a license, in order:
    • /etc/MultiTaction/Licenses
    • ~/MultiTaction/Licenses
    • ~/.MultiTouch/Licenses
  • macOS: Canvus client searches these folders for a license, in order:
    • /etc/MultiTaction/Licenses
    • ~/MultiTaction/Licenses

Canvus client reads every folder in the list. If it finds more than one valid license, it uses the one that expires last, whichever folder it is in. An expired or invalid license in the system-wide folder does not stop a valid license in your own folder from being used.

The license wizard and --activate save the license in the per-user folder of the account that runs them (%LOCALAPPDATA%\MultiTaction\Licenses on Windows, ~/MultiTaction/Licenses on Ubuntu and macOS). To license every account on the computer, copy the license file into the system-wide folder.

Where is screen.xml?

The location of screen.xml (see configure-graphics-coordinates) depends on the operating system:

  • Windows: Canvus client searches these locations for screen.xml in order:

    1. %APPDATA%\MultiTouch\screen.xml
    2. %PROGRAMDATA%\MultiTaction\screen.xml

    Where %APPDATA% refers to the user profile of the user running Canvus client (e.g. C:\Users\multi\AppData\Roaming).

  • Ubuntu: Canvus client searches these locations for screen.xml in order:

    1. ~/.MultiTouch/screen.xml
    2. /etc/MultiTaction/screen.xml

    Where ~/ refers to the home folder of the user running Canvus client (e.g. /home/multi).

  • macOS: Canvus client searches these locations for screen.xml in order:

    1. ~/Library/MultiTouch/screen.xml
    2. /etc/MultiTaction/screen.xml

    Where ~/ refers to the home folder of the user running Canvus client (e.g. /Users/multi).

Note

If Canvus does not find a copy of screen.xml in either location, it automatically creates a default configuration in the location under current user profile.

If you want to use a system-wide configuration, remove any screen.xml file under the user's profile and ensure the system-wide configuration file exists.

Where is config.txt?

The location of config.txt (see configure-input-mapping) depends on the operating system:

  • Windows: Canvus client searches these locations for config.txt in order:

    1. %APPDATA%\MultiTouch\config.txt
    2. %PROGRAMDATA%\MultiTaction\config.txt

    Where %APPDATA% refers to the user profile of the user running Canvus client (e.g. C:\Users\multi\AppData\Roaming).

  • Ubuntu: Canvus client searches these locations for config.txt in order:

    1. ~/.MultiTouch/config.txt
    2. /etc/MultiTaction/config.txt

    Where ~/ refers to the home folder of the user running Canvus client (e.g. /home/multi).

  • macOS: Canvus client searches these locations for config.txt in order:

    1. ~/Library/MultiTouch/config.txt
    2. /etc/MultiTaction/config.txt

    Where ~/ refers to the home folder of the user running Canvus client (e.g. /Users/multi).

Note

If Canvus does not find a copy of config.txt in either location, it automatically creates a default configuration in the location under current user profile.

If you want to use a system-wide configuration, remove any config.txt file under the user's profile and ensure the system-wide configuration file exists.

Where is Canvus client application binary?

The Canvus client application itself (mt-canvus-app.exe on Windows and mt-canvus-app on Ubuntu and macOS) can be found in the following locations:

  • Windows: %PROGRAMFILES%\MT Canvus\bin
  • Ubuntu: /opt/mt-canvus-<version>/bin, also reachable as /opt/mt-canvus/bin
  • macOS: /Applications/MT Canvus.app/Contents/MacOS

Tip

On Ubuntu, the folder name includes the version, for example /opt/mt-canvus-26.09.5/bin. Only one version of the Canvus client can be installed at a time: installing a new version replaces the previous one. From Canvus 26.09.6 the package also points /opt/mt-canvus and the command /usr/bin/mt-canvus-app at the installed version, so /opt/mt-canvus/bin works whatever version is installed.

Launching on macOS

On macOS, open the application normally (from Applications, Spotlight or Launchpad) rather than running mt-canvus-app directly. Opening the application runs a wrapper that sets the asset search path, the Qt plugin path and the bundled gflags interposer that the client needs to start. Calling the binary directly is only intended for the command-line licensing options; see the macOS install guide.