|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Announcements
Want a new Job?
Chapters
Services
Feature Zones
|
IntroductionTired of recreating an Options dialog for every application you make? Using this component, you can specify a hierarchical structure in the registration database under a vendor and application specific key, and automatically read, construct, and update the settings with minimal code. Or, if you store your settings somewhere else, you can use the component in Manual mode and read and save them at your will. A sample project and a help document is included. To add the component to the Components tab of your toolbox, compile the solution and then select the Components toolbox tab, right-click and select Add/Remove item..., then navigate to the OSSystem.ApplicationOptions.dll file, and select it. Add the component to a form and off you go! Registration DataOnce the
The Options key is the base options key. Other keys located under this are Category keys. Values within the keys are options. The options have special formatting, but don't let that bother you...the component takes care of creating and managing these for you. There are methods on the DialogsThere are two type of dialogs: Tabbed view and Tree view. A tabbed view presents hierarchical data as a set of tabs nested inside tab pages. As you can imagine, if the hierarchy gets too deep, the tabbed view loses its appeal. The tree view presents its data much like the Visual Studio Options dialog, and nesting is not a problem there since it only displays the options for one category at a time. Many properties of the
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||