|
Specifications
|
|
# 853 2LPSPRO11
|
LPS Pro
|
|
# 853 2LPSNET11
|
LPS Network
|
|
# 853 2LPSSTU11
|
LPS Student
|
|
# 853 2LPSSTPRO
|
LPS Student Upgrade to Pro
|
|
|
LPS 1.2.6 NEW FEATURE LIST / BUG FIX LIST
This update adds some functionality and fixes some bugs from version 1.2.5. It is recommended
for all users.
|
New Features
|
Import Auto Matching
By default, the import screens in LPS attempt to match up the columns from the file to be
imported with their most logical match within LPS. This behavior may not always be wanted.
Therefore a new option is available in all the import dialogs which allows you to turn off
the auto matching feature.
|
Import Option Settings
All settings for the import dialogs are now stored in memory. This allows you to repeatedly
use the same settings without having to re-enter them each time you perform an import.
|
Export Text Qualifiers
When exporting lights, dimmers and stock inventory you can now specify whether or not you
want a text qualifier to be used. A text qualifier is either a pair of double or single
quotes that surrounds each piece of information in the file. Being able to specify if
you want to use one or not helps with compatibility between LPS and other applications
that may be expecting the data to be formatted in a specific manner.
|
Export Option Settings
All settings for the export dialogs are now stored in memory. This allows you to repeatedly
use the same settings without having to re-enter them each time you perform an export.
|
Circuit Per Unit Insert
By default when you add a unit to a lightplot and that unit has more than one circuit per
unit, LPS will automatically add additional rows for the appropriate number of circuits.
You can now turn this behavior off by unchecking the Use Circuit Per Unit Insert option
under Edit -> Preferences -> Editing. With the option off, LPS will not insert additional
rows regardless of the number of circuits per unit associated with the entered instrument.
|
|
|
Bug Fixes
|
Fixed (Sorting By Custom Fields):
If you specified either a primary or secondary sort column to be a custom field, LPS would
not sort the layout by that field. Your data would appear in a random, unsorted manner.
This has been fixed and the layouts now sort properly for all custom fields. Note that a
custom field is always considered to be a string of characters and will be sorted in that
fashion.
|
Fixed (Defining A Custom Field As A Sort Column):
If a primary or secondary sort column of a layout was defined as a custom field, that
definition would not be saved. The next time LPS was opened, the sorting column would
have reverted back to its original state. This has been fixed and all primary and
secondary sort columns are saved properly.
|
|
|
