From: Werner S. <ws...@se...> - 2003-12-29 13:17:10
|
On Monday 29 December 2003 07:14, Mathias Lundgren wrote: > Last commit to muse shortcut config: > - Added dynamic shortcuts for all menu options in the arranger (will > hopefully work fine when config is loaded before menus are built) > - Added check and prevention of conflicting shortcut sequences inside > respective categories, global shortcuts (play/stop etc) and misc "reserved" > shortcuts (f.ex. Ctrl+C, Ctrl+V) > - Misc other shortcut-stuff... > > Happy new year! > > /Mathias i've recently changed the configuration logic to do the following: When the user changed configuration muse->changeConfig(true) is called. This saves the configuration data to ~/.MusE and emits the signal configChanged(). All widgets which use some configuration data (fonts, colors, shortcuts etc.) register to this signal and can update their configuration when called. Some widgets implement the method configChanged() for this. The user sees: - no more explicit "save configuration" Configuration is implicit saved when the user clicks "OK" in some configuration dialog - configuration changes are instant visible/usable (no restart of MusE necessary) For configurable shortcuts i suggest the following changes: move alle shortcut configurations into a configChanged() widget method. Connect configChanged() to application signal configChanged(). Call muse->changeConfig(true) in shortcut editor, when the user changed an shortcut. Werner |