Applying whole heaps of things in FormPreferences has no effect on the 
current instance of LyX. the user must first save the change then restart to 
activate the change. Is this slated for change?

At the moment the mechanism does not exist to change things like the bind 
files or ui files on the fly as the relevant code is buried within the 
private part of class LyX. Perhaps the time is coming for class LyX to be 
accessible from other parts of LyX. Eg, a (LyX *) in LyXView, together with a 
LyX::Dispatch() method?

Angus

Eg

lyxrc.override_x_deadkeys
        used in lyx_main.C
        // Bind the X dead keys to the corresponding LyX functions if
        // necessary. 
        if (lyxrc.override_x_deadkeys)
                deadKeyBindings(toplevel_keymap);

Similarly with the ui and bind files.




        

Reply via email to