View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004972 | MMW v4 | Framework: Scripts/Extensions | public | 2008-11-27 10:14 | 2009-06-05 14:20 |
| Reporter | peke | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.1 | ||||
| Target Version | 3.1 | Fixed in Version | 3.1 | ||
| Summary | 0004972: 'Options' button on Extensions dialog doesn't work in some cases | ||||
| Description | Options in extension Form do not function correctly. With Current Design Options Button is enabled if [Header] contains these two lines: ConfigurationScript=<ConfigurationScript> ConfigurationProcedure=<ConfigurationProcedure> Due the fact that most Scripters already make Setup Sheet it would be wise that we change those two lines to three lines which will allow Scripter/Developer to write only one Setup Sheet which can be used in Options Button and in Options Sheet: ConfigurationScript="ConfigurationScript.vbs" ConfigurationInitSheet="InitSheet" ConfigurationSaveSheet="SaveSheet" What we will make available is that new Modal Form is created with same attributes like Options Sheet and it will parse InitSheet( sheet) argument like in options, same thing for SaveSheet( sheet). .--------------------------------. | <Extension Title> - Options ### | |--------------------------------| | ##################### | | ##################### | | #### Options Sheet ####### | | #### From InitSheet ###### | | ##################### | | ##################### | |_______________[OK]_[Cancel]_| | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=2&t=17455&st=0&sk=t&sd=a&start=105 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1249 | ||||
|
|
This should be much intuitive than Current implementation? |
|
|
I'm not sure that I follow the above, however, if I can restate the problem, it is that in the Extensions dialog, when the last.fm extension is selected, the Options dialog is Active (i.e. not greyed out), but doesn't actually do anything. Users would expect that clicking 'Options' within the extensions dialog would either: a) open up a config panel associated with the Extensions dialog (in cases where Extension configuration is not in Tools > Options b) open up the Tools > Options > <extension> dialog Hopefully the above requirements are easily satisfied. |
|
|
b) could break Functionality in Party Mode and allow access to Mm settings. |
|
|
Fixed in build 1209. - There was ShowOptions method added to scripting, which allows the needed functionality without adding other installed settings. |
|
|
It is not resolved (1209). The Options buttons is enabled, but when I click on it, nothing is happening. |
|
|
I think that Jiri only added the ShowOptions method that allows to show options via the ConfigurationProcedure. So it is up to Peke to finish the script, am I right? |
|
|
> So it is up to Peke to finish the script, am I right? "script"? I think something is wrong with the program itself. Just to explain again what I already said in the mentioned thread - I added new dialog procedure stated in ConfigurationProcedure to my script, I added new form with Set oForm = SDB.UI.NewForm to this procedure... Still nothing. |
|
|
Status of this issue is wrong for a long time. It is not resolved as I explained. Could you change this, please? |
|
|
Ludek, can you look into it? |
|
|
Zvezdan is right, it doesn't work. Fixed in build 1249. |
|
|
Verified 1250 |
