Leadtools.Barcode Namespace > BarcodeData Class : Value Property |
[CategoryAttribute(" Data")] [DisplayNameAttribute(" Value")] [DescriptionAttribute("Data as an ASCII string value")] public virtual string Value {get; set;}
'Declaration <CategoryAttribute(" Data")> <DisplayNameAttribute(" Value")> <DescriptionAttribute("Data as an ASCII string value")> Public Overridable Property Value As String
'Usage Dim instance As BarcodeData Dim value As String instance.Value = value value = instance.Value
[CategoryAttribute(" Data")] [DisplayNameAttribute(" Value")] [DescriptionAttribute("Data as an ASCII string value")] public virtual string Value {get; set;}
@property (nonatomic, copy) NSString* value;
public String getValue() public void setValue(String value)
CategoryAttribute(" Data") DisplayNameAttribute(" Value") DescriptionAttribute("Data as an ASCII string value")
get_Value();
set_Value(value);
Object.defineProperty('Value');
[CategoryAttribute(" Data")] [DisplayNameAttribute(" Value")] [DescriptionAttribute("Data as an ASCII string value")] public: virtual property String^ Value { String^ get(); void set ( String^ value); }
The Value property simply calls GetData and internally SetData to get or set the data inside this BarcodeData as an ASCII text value.
Some barcodes like QR and PDF417 support data that is not necessary ASCII text. For example, an image, a URL or just raw stream of bytes. For these barcodes when reading a barcode, the Value property may not return an accurate representation of the data. Instead, use the BarcodeData.GetData method and parse them yourself. Also, when writing barcodes, you must set the raw data using the SetData method
The Australian post barcode (BarcodeSymbology.AustralianPost4State) string has a special format to distinguish different fields (i.e. FCC, DPID, and CIF). The string format puts dashes between fields as follows: "FCC-DIPD-CIF", where FCC is a 2-digit field (valid values are 11, 87, 45, 92, 59, 62, and 44), DPID is an 8-digit field representing the address, and CIF (optional) represents the customer information field. For more information, please refer to the standard. This string format applies for both read and write.
GS1 Databar Expanded (BarcodeSymbology.GS1DatabarExpanded) and GS1 Databar Expanded Stacked (BarcodeSymbology.GS1DatabarExpandedStaceked) barcode strings need to be written conforming to a string format that indicates a particular encoding method, such as Method "1", Method "0100", Method "0101", … etc. For example, a string (01)00012345678905(10)ABC123" is encoded using Method "1" (i.e. General Identification Data). Note that 14th digit of the item identification number (in this case, "5"), if it exists, is considered as a check digit and is ignored. A string that is written without following any of these special encoding formats will be encoded by Method "00" (i.e. General Purpose Data).
When a BarcodeData is returned from a read operation, an extra digit in curly brackets (i.e. "{" and "}") is added to indicate the linkage bit at the beginning of the string. The curly brackets are not part of the encoded barcode data, and they are not defined in the standard. Rather, they distinguish the linkage digit from other data. For example, if a barcode is written with string "(01)00012345678905(10)ABC123" while the linkage bit is set to zero, the read function result will be "{0}(01)00012345678905(10)ABC123", where {0} is the linkage digit and the remaining characters are the barcode data.
Some barcode symbologies contain extra information that are not available in BarcodeData, for these types, LEADTOOLS adds derived classes to contain the extra information. Refer to BarcodeData for more information.
For an example, refer to GetData.