On 4/5/05 8:38 AM, Joerg Barfurth [EMAIL PROTECTED] wrote:
deleted
You can restrict access to individual settings by providing a
configuration data (.xcu) file and using the protection attributes
(oor:finalized and oor:mandatory) in that file to mark individual
settings or entire
Hi Brian,
Brian Raymond wrote:
I wanted to see if anyone had any input on this. I've seen some good data on
how to make a custom schema for configuration data for my component but no
way to restrict access to it.
There is no way to do this in the schema.
I'm implementing some custom configuration
I wanted to see if anyone had any input on this. I've seen some good data on
how to make a custom schema for configuration data for my component but no
way to restrict access to it.
I'm implementing some custom configuration properties for my component that
should only be changed by
