Signature field: Difference between revisions

From Memento Database Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
<div align="right"><small>''&laquo; as of 2016-08-25, editions Mobile 3.9.7, Desktop 1.0.3 &raquo;''</small></div>
<div align="right"><small>''&laquo; as of 2016-08-29, editions Mobile 3.9.7, Desktop 1.0.3 &raquo;''</small></div>
-----
-----
A Signature field may contain a link to the stored image of a signature.
A Signature field may contain a link to the stored image of a signature.
Line 27: Line 27:


; Dependencies : Ability to add one or more visibility dependencies upon fields with qualifying types.
; Dependencies : Ability to add one or more visibility dependencies upon fields with qualifying types.
[[Category:Spec]]

Revision as of 00:35, 29 August 2016

« as of 2016-08-29, editions Mobile 3.9.7, Desktop 1.0.3 »

A Signature field may contain a link to the stored image of a signature.

The Free Mobile Edition allows for one signature to be stored. The Pro Mobile Edition allows an unlimited number of signatures to be stored.

When importing and exporting, the full pathname to the signature image file is used.

The signature image is not stored in the database. If files have been moved to another location, you can automatically change the links: library > right slide menu > files> menu > find missing files.

You can set the directory for files : settings > file storage.

Name and Hint

Standard across all field types.

Advanced Parameters

Paint options
Because the signature is captured within the application, these options describe the height & width of the paint box, the brush size & color and the background color to be used for capture & display.
Required
Make entry of a value mandatory before saving an entry

Display Options

Display in the list as
Select among the following roles for the current field:
  • As a Regular field
  • As a Thumbnail
Display field name in Entry Edit Card?
By default, yes.
Dependencies
Ability to add one or more visibility dependencies upon fields with qualifying types.