Just an idea, but could you use an xbl:inherits attribute to set the preference using your binding? Essentially, put a preference attribute in the tag where you call the binding and then in your content, have the correct xul element (textbox or whatever) inherit that property from the xbl tag?

Matt

On 12/9/05, Nickolay Ponomarev <[EMAIL PROTECTED]> wrote:
I believe you should put something like this in one of your prefpanes:
  <myelement preference-editable="true"/>
Where the binding of myelement has a "value" property.
This should make the "value" setter called at startup

To inform the system of changes of your widget's value, one of these
events must be fired: change, command, or input.

Nickolay

On 12/9/05, Pekka Sillanpää <[EMAIL PROTECTED] > wrote:
> Hi all!
>
> I have one custom XBL element in my extension, and now when I am
> starting to use the prefwindow/preference stuff, I face problems. I have
> no idea how to set (initialize) the preference for a custom element. So
> when I open my settings panel, the custom XBL binded text box is empty.
> For the default textbox, checkbox etc. elements it is straightforward.
>
> How can I specify the field of a custom XUL element that the
> <preference> element should modify and read?
>
> I have read:
> http://developer.mozilla.org/en/docs/Preferences_System:New_attributes
>
> And there were said:
> "If you wish it to update the value of an element with different local
> name, for example your own XBL widget, you need to set the
> |preference-editable="true"| attribute on it."
>
> Set it where?
>
> Thanks in advance!
>
> Pekka
>
> _______________________________________________
> Project_owners mailing list
> [email protected]
> http://mozdev.org/mailman/listinfo/project_owners
>
_______________________________________________
Project_owners mailing list
[email protected]
http://mozdev.org/mailman/listinfo/project_owners

_______________________________________________
Project_owners mailing list
[email protected]
http://mozdev.org/mailman/listinfo/project_owners

Reply via email to