View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011468 | MMW v4 | Framework: Scripts/Extensions | public | 2013-11-10 10:04 | 2013-11-10 10:09 |
| Reporter | zvezdan | Assigned To | |||
| Priority | none | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Summary | 0011468: Shortcut key from Scripts.ini should be related to Action list in Options\Hotkeys | ||||
| Description | Let say that I have some script of type 0 or 1 which has Shortcut key set to the Scripts.ini during the installation. It would be nice if the program detect that and change its entry in the Action list appropriately by adding one new item to the list, e.g. General: Execute script: Find Currently Playing track with the corresponding Hotkey value. That detection by the program could be done after applying SDB.RefreshScriptItems. Alternatively, you could refresh the Action list by reading Shortcut keys from the Scripts.ini file on the restart of the program. However, I prefer the first suggestion with the RefreshScriptItems because it doesn't require restart. Also, when the user change hotkey for the script using the Action option in the Options dialog, that modification should update the Scripts.ini file appropriately. Here is what we have now: 1. my script has Shortcut = Ctrl+Alt+F set to Scripts.ini during installation; if user wants to change that hotkey, one should add the corresponding script to the Action list since that shortcut is not automatically added to the list. 2. if user change Hotkey to e.g. Shift+Ctrl+F, the Scripts.ini will still contain Shortcut = Ctrl+Alt+F key. However, the Tools\Scripts menu will show correctly Shift+Ctrl+F. 3. If user removes the corresponding item from the Action list which is previously added (Shift+Ctrl+F), the program will not react to the default Ctrl+Alt+F hotkey until the restart of the program. 4. Let say that someone actually wants to remove completely the hotkey for my script. User cannot do that permanently using the Action list, but only if one removes manually the Shortcut key from the Scripts.ini file. If you implement my suggestion, when user removes the corresponding item from the Action list, the Shortcut key in the Scripts.ini would be cleared and my script will not react to the default key anymore. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
