Default & Locked Settings

Bug #717088 reported by KHobbits on 2011-02-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

It would be nice if these two scripts allowed some easy way for other scripts to register user (tag) settings in a way that would allow them to be managed from within these scripts.

Infact one solution could be to allow settings to be completely managed from within these scripts simply by registering them, something akin to the registerifacecmd function, saving each script from coding the command internalbind event.

One example would be the auth script, it would be useful to provide a default setting to authphrase.

I'm not completely convinced of this requests merit, I'll have to think about it.

Thinking about this request I remembered I actually had the same idea while writing these scripts. Since I still arrive at the same conclusion now as then, I'm declining this request due to the following two reasons:

- It is by no means guaranteed that custom settings are actually set via the "set" command, take e.g. my old nickserv.tcl script
- Each custom script provides its own iface2 commands and I don't see any clean way to provide override commands for them, especially when you consider that they might have their own input validation.

I do agree however that the provision of settings via tcl scripts needs to be revamped and I already wrote a feature request for it. This will however only be considered for version 1.4 and then implemented directly in the tcl module along with a new bind structure.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers