• Nullability: It is nullable by setting the Value property to null or DBNull. The Text property can also be set to an empty string. When set to null, an optional custom string can be displayed, e.g. "Type to set" or "No data". The user can also force the content to null. It’s up to the developer how this is done ("delete" key press, checkbox or another button with text or a custom image). This screencast, demonstrates the feature from the user point-of-view.
  
  
• Databinding: SFPE goes beyond what you expect from DataBinding. The Value and Text properties can, of course, be bound to a data source, but the features do not stop here. Since the component is nullable, there’s no problem binding to a nullable column in a grid. Also, each field can be bound independently. This means that the value of the checkbox itself can be controlled by its own boolean column.
  
  
• DataGridView and PropertyGrid integration: A custom editor, implementing IDataGridViewEditingControl, enables you to embed the DateTimePicker in your DataGridView. Your grid gets all the benefits of the editor, including DataBinding with a nullable DateTime column. This screencast (from the initial beta) showcases the perfect integration. If you also have SPG, a custom feel integrates the DateTimePicker into the PropertyGrid. (This fixes the initial issue of SPG not being able to include the Microsoft DateTimePicker, which is not flexible enough.) Because the BorderStyle can be set to None and the text offset can be changed, SFPE can be embedded in other 3rd party containers. Contact VisualHint if you have specific requirements.
  
  
• Date and time formatting: Unlike the legacy DateTimePicker, SFPE handles all the "Standard DateTime Format Strings" and "Custom DateTime Format Strings". This means you can use for example the RFC1123 pattern (code 'R') or the seconds fraction format specifier (e.g. code 'fff').
  
  
• Appearance: All the usual properties determine the appearance of the control. Set the font, the foreground and background color when enabled or disabled, the width of the fields as fixed (like Microsoft DateTimePicker) or variable (displayed as a continuous string), and the separator width between them.
  
  
• Right to Left languages: Smart FieldPackEditor supports RTL. This is rare among 3rd party components. Here’s what an Israelian customer has to say about it:"I examined the control and let me tell you it is very professionally designed and implemented; way to go! Also the RTL and Hebrew are working great, a feat not easily performed by many professional companies."
  
  
• Built-in buttons: The DateTimePicker can natively show: a dropdown button, updown buttons and a checkbox. These are independent and can be shown at will. It’s also easy to add your own generic button for a custom function.
  
  
• Quick edition: Everything has been done to make editing easy for the user: * On completing the current field, the focus can automatically jump to the next. * Typing the first letter of a static field makes the focus jump to the next available editable field. * Auto-completion is available for fields such as day and month names.

A base framework

SFPE is a generic field editor. The base class, FieldPackEditor, is made of field packs, logical units capable of storing a value such as a latitude. Each pack is made of fields, for example the latitude "minute" field . Derive from the pack and field base classes to create the content of a specialized editor. Derive from FieldPackEditor to create a complete solution with methods and properties pertaining to this editor.

SFPE supports the following native features (those mentioned for the DateTimePicker are not repeated here):

Control of the dropdown window: Take complete control of the dropdown window (unlike with the Microsoft DateTimePicker). Use an API to open and close the popup as required, and to define its content. For example, change the default month calendar in the DateTimePicker or display a Google map under a latitude/longitude editor.

Management of packs and fields Remove packs and fields at will. Since they have unique identifiers, you can get a reference on one of them, then perform an operation on it such as selecting it, setting it as read only, or changing its culture or min/max values. Once you get a field, it’s easy to navigate to the other fields.

Flexible keyboard management Manage keys at the editor, pack and field levels, easily changing default behaviours. Packs and fields can specify the keys they accept. For example Ctrl+Home will be filtered by the pack (it resets a date to today for example) whereas a digit will be understood by a numeric field. A special mention for the TAB key: you can let it browse by fields, packs or nothing - handy, for example, for jumping from anywhere in the latitude pack to the first field in the longitude pack.

Numeric fields Rapidly create your own editable numeric fields using a specially defined NumericField base class.

Other specialized editors

To showcase its possibilities, SFPE comes with two ready-to-use editors: an IP address editor, useful in any network type application, and a latitude/longitude editor, useful in any GIS or similar application. These controls benefit from all above mentioned features.