Terminal commands

Boolean settings

Newly added resources auto resize

You can change the default option when new images are inserted to the document by using this command from the Terminal. This is unsupported and may potentially change in a future release.

Enable
defaults write com.tumult.Hype4 newResourcesAreSetToAutoResize -bool YES

Disable
defaults write com.tumult.Hype4 newResourcesAreSetToAutoResize -bool NO

^{source: https://forums.tumult.com/t/png-files-fail-to-show-in-preview-safari/15708/5}

Newly added resources preloading control

In the latest update, there's a new setting that allows you to control whether new images and other resources are preloaded when added to your document. By default, the application preloads all new resources, which helps ensure they are immediately available for use. However, if you need to manage system resources more tightly or prefer to load resources only when necessary, you can now disable this feature.

Enable Preloading
defaults write com.tumult.Hype4 newResourcesAreSetToPreload -bool YES

This command reinstates the default behavior where new resources are automatically preloaded.

Disable Preloading
defaults write com.tumult.Hype4 newResourcesAreSetToPreload -bool NO

Use this command if you prefer to turn off the automatic preloading of new resources. This can be particularly useful in projects with a large number of resources or when operating under constrained system conditions.

^{source: https://forums.tumult.com/t/hype-4-1-17-update-bug-fixes/23832/3}

Use color picker pop over

You can change the default behavior of the color picker to float or be a popover (being the default).

Enable
defaults write com.tumult.Hype4 useColorPickerPopOver -bool YES

Disable
defaults write com.tumult.Hype4 useColorPickerPopOver -bool NO

^{source: https://forums.tumult.com/t/floating-color-picker/18625/2}

Autosave documents (Apple persistence)

This terminal option sets the auto save feature in Hype. There is also no guarantee that this option will always work with new OS or app updates.

Enable
defaults write com.tumult.Hype4 ApplePersistence -bool YES

Disable
defaults write com.tumult.Hype4 ApplePersistence -bool NO

^{source: https://forums.tumult.com/t/disable-auto-save/15783/2}

Show all browsers and not only Tumult approved ones

This terminal option disables the Tumult whitelist for allowed preview browsers.

Disable, shows all browsers
defaults write com.tumult.Hype4 showOnlyApprovedPreviewBrowsers -bool NO

Enable (the default)
defaults write com.tumult.Hype4 showOnlyApprovedPreviewBrowsers -bool YES

^{https://forums.tumult.com/t/no-love-for-brave/15578/2?u=maxzieb}

Use the full versions of the Hype Runtime (non-minified)

This terminal option enables the use of unminified versions of the Hype Runtime. Note that this option creates an error (404) when using the official Hype Runtime CDN as that doesn't include full runtime versions.

Enable
defaults write com.tumult.Hype4 UseFullHypeJSTemplate -bool YES

Disable
defaults write com.tumult.Hype4 UseFullHypeJSTemplate -bool NO

^{https://forums.tumult.com/t/i-need-the-non-minified-version-of-the-code/14222/6?u=maxzieb}

Export the largest scene first

Since the introduction of posters the HTML outputted has the smallest scene size written to the DIV container. Even though the Hype document resets that the moment it gets rendered this might create a layout "jump" for the surrounding elements if you're not using the "mobile first" approach. The setting can be reversed to use the largest scene dimensions while loading.

Enable
defaults write com.tumult.Hype4 exportLargestSceneAsFirst -bool YES

Disable
defaults write com.tumult.Hype4 exportLargestSceneAsFirst -bool NO

^{https://forums.tumult.com/t/mobile-settings/18910/3?u=maxzieb}

Change the sort order when rendering the Hype runtime DOM

The Hype runtime DOM order is based on a top-left element location. This is to better help accessibility/assistive devices which use DOM ordering to read out the ordering of elements. We intentionally made this change in Hype v3.6. As older versions of Hype did DOM elements by z-index; this behavior is still part of the app through a hidden terminal command.

Enable export by z-order
defaults write com.tumult.Hype4 elementInsertionOrderSortMethod "compareByZOrdering:"

Revert to default
defaults delete com.tumult.Hype4 elementInsertionOrderSortMethod

^{https://forums.tumult.com/t/hype-emits-elements-in-dom-div-order-that-does-not-match-tool-view/20520/2?u=maxzieb}

Other settings

GIF-Rendering engine

In Hype 3.5 and prior, Hype used Apple’s GIF export instead of ImageMagick’s. Overall the ImageMagick engine typically produces better results and lower sizes, but this is content dependent and not always the case. If you want to see what Apple’s engine can provide, there is a hidden preference that can be activated in the terminal.

Let Apple create the GIF
defaults write com.tumult.Hype4 AnimatedGIFEngine Apple

Use ImageMagick built into Hype
defaults write com.tumult.Hype4 AnimatedGIFEngine

^{source: https://forums.tumult.com/t/problems-with-the-quality-of-gifs/16996/11}

Seeing arguments and capturing output from Export Scripts

In the course of developing an Export Script, you may be curious to get better visibility into what is being passed to your Script, and the output that Hype sees. You can enable Hype to log via enabling this default:

Enable
defaults write com.tumult.Hype4 enableExportScriptDebugLogging -bool YES

Disable
defaults write com.tumult.Hype4 enableExportScriptDebugLogging -bool NO

Or, if you are using a beta version of Hype, you must use this command:

Enable
defaults write com.tumult.Beta.Hype4 enableExportScriptDebugLogging -bool YES

Disable
defaults write com.tumult.Beta.Hype4 enableExportScriptDebugLogging -bool NO

You can then view the output by running this command in the Terminal (Sierra):

log stream --style syslog --predicate '(processImagePath contains[c] "hype") && (category != "security_exception")'

^{source: https://github.com/tumult/hype-export-scripts}