0008757: Disable d_iPhone plug-in in case of problems - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0008757	MMW v4	Synchronization	public	2011-11-24 10:14	2012-06-21 00:18

Reporter	jiri	Assigned To
Priority	urgent	Severity	major	Reproducibility	unable to reproduce
Status	closed	Resolution	fixed
Product Version	4.0
Target Version	4.1	Fixed in Version	4.0.6

Summary	0008757: Disable d_iPhone plug-in in case of problems
Description	A problem in QT can often cause MM to not start at all. Since the only know solution is to disable d_iPhone.dll, we could try to do so automatically in the following manner: 1. In case MM encounters any problem during QT initialization, it won't continue in standard operation (as done in MM 4.0 and previous versions), but will show user something like: 'It wasn't possible to correctly initialize iOS devices support, MediaMonkey can become unstable. Do you want to disable iOS support and restart MediaMonkey (recommended).' [[Yes]] [No]. 2. After clicking Yes, d_iPhone.dll would be renamed to d_iPhone.dll.off. 3. Note that MM wouldn't have enough rights to perform step 2. by default, so we might run a small helper application for this purpose (and any similar purpose if needed in the future for other tasks).
Tags	No tags attached.
Attached Files	devices.jpg (90,635 bytes) devices.jpg (90,635 bytes)

Fixed in build	1494

jiri 2011-11-24 10:15 administrator ~0029065	Assigning to Rusty for a review and wording suggestion.

rusty 2011-11-24 16:27 administrator ~0029069 Last edited: 2011-11-24 16:30	Wouldn't it make more sense to simply do this automatically? i.e. if MM can't start because of a problem during QT initialization, then MM should just automatically disable the plugin because otherwise MM can't start up. The next issue is how to re-enable the plugin after the user fixes whatever QT issues were problematic. I would propose a few changes to the Device panel, that allow the user to configure device plugins independently of devices. See attached. Note: if we create a 'helper application' to make such config changes, then we should also use it to fix the 'restart in admin mode after OS config changes' are made issue.

rusty 2011-11-24 16:35 administrator ~0029070	Another alternative approach re. the device plugins would be to treat them as extensions that are pre-installed with the app. e.g. the extensions panel would come with several extensions pre-installed (USB device addon, iPod/iPhone device addon, etc.) and we could add a function to temporarily enable/disable an extension without uninstalling it.

rusty 2011-11-24 21:42 administrator ~0029072	So for the headers, in order to minimize translation requirements: 1) Available Plug-ins (requires restart): Rusty will modify 'Available Devices / Plug-ins:' to 'Available Plug-ins' for all languages. And '(requires restart)': will be re-used. 2) Device Profiles: This string already exists.

rusty 2011-11-25 12:10 administrator ~0029079	One other thought: An even simpler approach might be to just leave the dialog as is (i.e. as it is in 1459), but change 'Show' to 'Enable' (which already exists). This would be simpler for now as it would avoid translation issues for 4.0.1. The workflow would be pretty much the same, i.e. if MM can't start because of the plugin, all instances of it would become disabled.

Ludek 2012-05-29 12:16 developer ~0031244 Last edited: 2012-05-29 12:16	I think there is no longer a need to fix this as 0009382 is fixed now. There is no longer any QT dependency in d_iPhone.dll

peke 2012-06-21 00:18 developer ~0031417	verified 1499