> | 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, t
Angus Leeming <[EMAIL PROTECTED]> writes:
| 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?
Yes, ideally.
| At the moment the mechanism does
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
