As mentioned earlier, commands that do not require object selection may use the Properties palette to display command-specific properties. Command property sources may provide either static or dynamic properties, or both.
Implementing command properties is similar to the procedures described for object-editing command synchronization. However, there is no need for a custom graphical object definition. Your command's application may use Property Inspector notifications to perform any permissible tasks.
If you wish to provide static command properties, you must implement a COM object that defines those properties. This object replaces the “COM Wrapper for Custom Object” module shown in Figure 2. You use the acedSetIUnknownForCurrentCommand() function to register your COM object and designate its “listener” implementation as the target of property notifications.
If your command uses only dynamic properties, the synchronization technique is simpler. You do not have to call the acedSetIUnknownForCurrentCommand() function to register your object, nor do you need to implement an object based on IPropertyNotifySink. Instead, you merely define your dynamic properties, and then register your command name with AutoCAD as a dynamic property source. This registrations is done with the GET_OPM_COMMAND_PROPERTY_MANAGER macro found in the inc\dynprops.h file.