View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006336 | MMW v4 | Framework: Scripts/Extensions | public | 2010-04-25 00:17 | 2010-11-24 16:52 |
| Reporter | zvezdan | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0006336: ISDBUIButton::Image property needed | ||||
| Description | It would be nice if buttons in scripts could have assigned icon or picture as a property. The argument could be for example SDBImage object with e.g. loaded .ico or .png file, but in that case ISDBImage::ImageData should be read/write property, not just read-only. I really need a possibility to assign an icon or picture to the button. I need it at least for Add, Del, Up and Down buttons. For example, I have an intention to implement multi-item artist control within the new properties sheets (v4.0) using the listview control and I need those 4 buttons for manipulating specific items in that control. I don't like to see "Add", "Del"... as captions on buttons, it could be much nicer to see pictures instead, as you have pictures on buttons beneath the Filter and Views listview in the Options dialog box. | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=19&t=51716 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
MM devs, how could I change Project for this issue? I realized that I wrongly put it in MediaMonkey Addons: Other, while it should be in Framework: Scripts/Extensions instead. |
|
|
Problem is that we currently don't have buttons with image support (not a standard Windows component), the image buttons shown currently by MM are actually toolbars with one toolbar button added. We could try to implement this as a component for scripting usage, but given the work needed, setting this a low priority and rather deferring after decision of cross-platform component set to be used. |
|
|
Well, if you are talking about Linux/Mac, then you could forget for all VBScript add-ons anyway. You know, I have always been wondering what would happen if you decide to go with cross-platform route. In that case all of this that we scripters made so far could be just dropped for nothing. This is serious decision and you should think very carefully what is more important to you - cross-platform implementation of the program without VBScript support or just Windows implementation with existing VBScript support. I think that you should tell us your plans about that right now, we scripters deserve to know if we waste our time on something which would be abandoned so soon. Maybe you have a plan to keep existing API and continue support for VBScripts under Windows at least? |
|
|
Well, we haven't made a decision on this subject yet, so there's nothing to publish at this moment. In any case, we don't have any intention to abandon all the scripts and their authors. In case there will be a cross-platform version, we'd like to support the existing VBScripts - at least on Windows, but probably also on other platforms using some emulation. Should you have any more questions, please e-mail me, I'd like to keep Mantis for discussions directly related to issues there only. |
