Liquid Studio 2020
User Interface Guide / Options / Environment / General Options
In This Topic
    General Options
    In This Topic

     

    Check for updates at startup

    By default, the application will check the Liquid server for updates, use the option to stop the check. Note: You should then use the Check for Updates option from the Help menu to manually check for updates on a regular basis. This can not be turned off if you are using the community or trial version.

    Write Banner Comment

    By default, the application will write branding into files created by the application. use this option to turn of branding.

    This can not be turned off if you are using the trial version.

    Report anonymous usage

    If this is checked then information about feature usage is periodically sent to us.
    This information helps us understand how our customers are using the application, and allows us to focus our efforts on features that are used the most, ultimately improving your user experience. 

    What is contained in these reports

    What usage reports do NOT contain

    Show Status Bar

    Shows or hides the status bar for the application

    Perform validation on load

    If this is checked, then when a document is loaded for the first time, it is validated. This can slow the application down if you are working on large documents.

    Perform validation when a document is selected

    If this is checked, then when a tab is selected, validation is performed on it. This can slow the application down if you are working on large documents.

    Show Start Page on startup

    The start page contains our news feed and Most recently used projects and files.

    Item Lists

    The number of files remembered in the Most Recently used Files list

    Default Encoding

    The encoding to assume when one is not supplied. Currently always utf-8.

    Write Byte Order Marker (BOM)

    This is a few bytes that is added to the start of a file. It allows other applications to determine the encoding that has been applied to the document, so that it can be interpreted correctly. Unicode files must have a BOM to identify them. The only time the BOM becomes an issue is with UTF8 files. For Utf8 there is no standard that says whether the BOM should be written or not. Most Microsoft application (and newer apps) write it out, some older apps don’t (and worse still don’t understand it when it's read in). In order to accommodate this we  write the BOM by default, but there is a global option to turn it off for UTF8.

    See Also