View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009073 | MMW v4 | Framework: Scripts/Extensions | public | 2012-02-02 17:37 | 2012-02-02 17:41 |
| Reporter | zvezdan | Assigned To | |||
| Priority | none | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0009073: Option to specify Enabled, Visible and Active for items in the Scripts.ini file for type 0/1 scripts | ||||
| Description | There are some situations when some item from the Tools|Scripts menu should be disabled/hidden like any other menu item created by scripts in other menus, e.g. File or Edit. For example, I have a script with two entries in the Scripts menu: "Add Currently Playing Track to Playlist" and "Add Selected Track(s) to Playlist". The first item should be enabled only when the program is playing some track and the second item should be enabled only when there are some selected tracks. So, it would be nice if we could specify Enabled = False in the corresponding section of the Scripts.ini file and after that apply SDB.RefreshScriptItems to get those menu items disabled. Similarly, there are some situations when some script from the Scripts menu should be temporarily hidden without its uninstalling. There we could have two options: 1) the menu item is hidden and the Action list of the hotkeys has removed its entry; for that we could use Visible = False, Active = False; 2) the menu item is hidden, but the Action list still displays that entry and, more importantly, the press on the specified hotkey should start the corresponding script even when it is not visible in the Scripts menu; for that we could use Visible = False, Active = True. This second option is especially interesting to me. For example, I have Expand All script which expands all sub-nodes of the selected node by press on Num * hotkey. I have that item in the tree pop-up but, as I reported before, Shortcuts specified for items in the tree pop-up menu don't work at all, so I need to create item in the Scripts menu for that. It is OK to me, but it would be nice if that item is not visible in the Scripts menu, only active because of its hotkey. Why it should not be visible? Well, the answer is simple - it adds unceasingly one more item to the already overcrowded menu, while its use from that menu is unintuitive. You see, why would anybody want to expand sub-nodes of the selected node by using some item from the Scripts menu? Here is another example why I would want to have item in the Scripts.ini file with active hotkey, but I don't want to see its item in the Scripts menu. I have Queue List script that has F3 hotkey which allows adding of the selected tracks to some playlist. That hotkey is hard-coded in the script, but it would be nice if users could change it using the Hotkey sheet in the Options dialog. So, I could add one more item in the Scripts.ini file to enable that, but in that case I would get one more item in the Scripts menu which would be unintuitive and confusing since I already have it in the Play menu. As you could see, this is my practical suggestion how you could implement my another request: "Option to add Shortcut of some menu item to the hotkey's Action list in Options dialog needed". | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
