Skip to main content

Settings and commands

This guide covers Lore commands from the UI and advanced settings available in Anchorpoint, including workflow commands, repository management, and configuration options.

Changed files page​

The Changed files page lists every file that you have modified, added or deleted since your last commit. Use the checkboxes to pick the files that should go into the next revision. The checkbox in the Info column header checks or unchecks all files at once, and the right click menu on an empty area offers Check all and Uncheck all as well. Files that are not checked stay as changed files and can be committed later.

Type a message in the Describe what you have done... field. The first line becomes the title of the revision, everything below it becomes the description.

Submit​

The submit button combines several Lore commands together, such as stage, commit, sync and push. Per default, Anchorpoint will commit your changes, then sync the files from new commits that are on the same branch and then performs a push to publish your changes. This works in case you don't have any file conflicts. In case of conflicts, it will only create a local commit and then ask you to resolve the conflicts first, before pushing your files to the server.

See Submit and push behavior for the setting and Resolving conflicts for what happens when files clash. The keyboard shortcut is Ctrl+Return (Cmd+Return on macOS).

Commit​

This is a regular Lore commit, that will create a "checkpoint" of all your selected (so called staged) files. The commit will be created locally, and you have to push it to the server from the Revisions page.

You can reach it through the small arrow next to Submit, by holding Alt while the message field has focus, or with Ctrl+Alt+Return. If your project has no repository URL, Commit is the only option.

Revert​

Right click on one or several files and choose Revert to throw away your changes:

  • Deleted files will be restored
  • Newly created files will be deleted
  • Modified files will return to their previously committed state

Attention, this command is not undoable. Revert is useful if you experimented on a scene, downloaded assets to try them out and only want to commit the ones you actually used.

Other file commands​

The right click menu on a file also offers Show in Explorer (Finder on macOS), Show in browser to jump to the file in the Browser page, Open to launch it in its application, View in sidebar and View in overlay to preview it, and Thumbnail to replace the thumbnail with a screenshot. Hovering over a file shows a Compare button that shows the difference to the last committed version.

Revisions page​

The Revisions page shows the history of your current branch. Local revisions that are not on the server yet are listed at the top with an orange upload icon. Revisions that are on the server but not on your computer yet are shown with a blue download icon. The counters in the status bar at the bottom of the application show the same numbers and take you to the page.

Push​

Uploads your local revisions to the Lore server, so your team members can sync them. The button is highlighted when there is something to push. The first push of a new branch also publishes that branch.

Sync​

Downloads new revisions from the server and applies them to your files. If your changed files would be overwritten, the sync stops and asks you to move those files to a branch first, see Resolving conflicts.

Merge and Checkout​

These buttons appear while you are previewing another branch, or when your branch is behind main. They are described on the Branching page.

Undo Revision​

Right click on a revision and choose Undo Revision. This restores every file the revision touched to the state before that revision and puts them into your changed files. Nothing is removed from the history. Commit the changed files to record the undo. You can select several revisions and undo them together.

Anchorpoint warns you if a file has changed since that revision, because the undo will overwrite that later change. Revisions that are only on the server cannot be undone before you sync.

Checkout Revision​

Sets all files in your project to the state of the selected revision. If there are pushed revisions after it, you can get back to the latest state by syncing from the server. Unpushed revisions after it are removed from the branch, and changed files are lost, so Anchorpoint asks you to confirm with Continue and Discard Changes. This only works for revisions on your current branch.

Copy Id​

Copies the id of the selected revision to the clipboard. This is useful when using the Lore command line.

Restore​

Click on a revision to see its files in the right sidebar. Hover over a file to Compare it with the previous version, or right click on it and choose Restore. You have two options:

  • Overwrite: Overwrites the current file version with the version from the revision you selected.
  • Keep Original: Does not touch the current file and creates a new file next to it.

Restored files show up as changed files, so you can commit them.

Filter​

Use the magnifier in the page header or press Ctrl+F to filter the revisions by message, author or revision id.

Branching commands​

Creating, viewing, switching, merging, publishing and deleting branches all happen in the branch overview, which opens when you click on the branch name in the breadcrumb bar or in the status bar. Every command is described on the Branching page.

Lore settings​

Settings can be accessed by clicking on the gear icon in the bottom right corner. You can navigate through application settings and Lore settings that are either tight to your current Lore repository or applied globally (the personal page) accross all repositories.

Project settings​

General lets you change the Project name that Anchorpoint lists the project under. The folder on disk keeps its own name. Delete project removes the project from Anchorpoint but keeps all files on disk.

Lore shows the Repository URL of the Lore server the project is connected to.

Application settings​

  • Enable single click for folder navigation: Opens folders and projects with a single click on their name. On by default. Useful for tablets.
  • Enable single click for opening files: Opens files in their default application with a single click on their name. Off by default; a double-click always opens a file.
  • Show hidden files and folders: Shows files and folders whose name starts with a dot in the Browser page and the folder tree. The Changed files page always shows them, so they can be committed.
  • Send crash reports: Sends a report to Anchorpoint when the application crashes. Takes effect after a restart.
  • Send usage statistics: Sends which features are used, the app version and the operating system. Never includes file names, paths or project content.

Account​

Shows the account and server you are signed in with, and lets you Sign out or Sign in to Anchorpoint.

Lore (personal)​

Author name is shown as the author of everything you commit. It is taken from your Anchorpoint account. Without an account you can type any name here. Leave it empty to use the user name of your computer.

Submit and push behavior​

This setting decides what happens when you click on Submit and there is a new revision on the server that you do not have yet.

  • Sync first, then push: The changes on the server are combined into your files first, and your work is published afterwards. If the sync leaves conflicts, you resolve them before it is published.
  • Don't do anything automatically: Your push is refused while there are newer changes on the server. The commit stays safe on this computer until you sync and push it yourself.

Pick Sync first, then push if you prefer a history where merges happen on your computer, and Don't do anything automatically if you want to control every step yourself.

Lore CLI commands​

Anchorpoint has an inbuild terminal to evoke any kind of Lore command on the repository. You can access it by clicking on Console in the bottom right corner of the application or by pressing Ctrl+J.

The console is a regular shell (PowerShell or Command Prompt on Windows, your default shell on macOS and Linux, switchable in the console header) that starts in the folder of your project. The lore command line tool bundled with Anchorpoint is on the path, so you always use the same Lore version as the application itself. Tab completion for lore commands is set up automatically in PowerShell, bash and zsh.

lore --help

The Log tab next to the terminal shows what Anchorpoint is doing in the background, which helps when reporting a problem.