Tools - Options

Specify user preferences.




Choose the rendering engine that is used to create displays and to render layouts for printing.




Hardware acceleration in the above using GPU is not parallel computation as described in the GPGPU topic.   Instead, it is simply using a GPU for faster graphics rendering.    GPGPU computational parallelism requires a reasonably recent NVIDIA GPU; however, using a GPU for faster graphics works with almost all GPUs (AMD, Intel, NVIDIA) that are supported by Microsoft Windows for graphics rendering.


Specify the size of internal memory cache used by 64-bit Manifold, using either automatic cache sizing or providing an explicit value in gigabytes (GB).  Manifold must be restarted for any change in cache size to take effect.   This option is ignored by 32-bit Manifold instances, which in any event are limited by 32-bit Windows operating system limitations to memory sizes smaller than reasonable cache sizes.  


Increasing cache size can help performance of some operations, but can also hurt performance depending on what is being done.  A rule of thumb is to set a cache size no larger than one-half the total size of installed physical memory, or slightly less than half of installed physical memory when regularly running multiple instances of Manifold.  Choosing (auto) is conservative and always safe.




Setting the cache parameter allows users to allocate use of memory based on how they intend to use Manifold.   For example, if we know we will routinely have five different projects running in five different Manifold sessions, we would not want the first such Manifold session launched to grab all available memory, leaving too-small amounts of memory available for the other four sessions.   Choosing (auto) results in conservative (relatively less) memory allocated to each Manifold session.  


In contrast, if we know we will be running just one Manifold session on a machine with 64 GB of memory installed we can set cache size to 48 GB so that one Manifold session will grab and use lots of memory regardless of what else is going on in the system.


Default coordinate system for new components

btn_coord_sys_picker.png  Click the coordinate system picker button to specify the coordinate system that will be used when a new, blank component is created.




Manifold raises confirmation dialogs to confirm deletions and exiting the application.   Confirmation dialogs can be removed by checking the Never show this again box in the confirmation dialog, or by unchecking the options below.  Note that checking the Never show this again box in a confirmation dialog for deleting layout frames, objects in drawings, labels, or records in tables will remove the use of a confirmation dialog in layouts, drawing layers, labels, and tables.







Default coordinate system - Newer software like ESRI's ArcGIS Pro and Manifold tend to use Pseudo-Mercator as a default coordinate system because that is the coordinate system almost universally used by web servers.    In modern times web servers have become a dominant source of data for base maps and backgrounds for custom maps.  Using Pseudo-Mercator also ensures that measurements tend to make sense because the units of measure are genuine linear units such as meters.


Older software packages like Manifold Release 8 and QGIS tend to use Latitude / Longitude as the default coordinate system for new components.   That made sense in a day when shapefiles could not be relied upon to convey projection information, and it can also be handy today for dealing with geocoded data maintained in text form as lists of latitude and longitude degree coordinates.


But using Latitude / Longitude requires a mental hack when displaying drawings because degrees are angular units, not linear units as a rectangular drawing implies.   When using Latitude / Longitude we are buying into a conceptual slipperiness by using angular units in such a setting. That can  trip us up, for example, by how the unit of measure, degrees, expands and contracts as we move north and south.


If we are going to be doing a lot of work with data from older software in older formats where we know it is almost all going to be in Latitude / Longitude with no projection information provided, then it may be useful to switch the default coordinate system for new components to Latitude / Longitude.   It is also not a bad idea to use Latitude / Longitude when working with point data kept primarily in text lists of latitude and longitude degree coordinates.  We can always show such data in a Pseduo-Mercator map window and let Manifold re-project the data on the fly for display.


Status Bar Options - Options for the status bar, such as what format to use to display mouse cursor location, are set in the Status Bar - Position and Status Bar - Location panes.


See Also







Change Coordinate System


Coordinate System


Status Bar - Position


Status Bar - Location