0016825: Device Options: Profile Manage settings can Miss Device Image

ID	Project	Category	View Status	Date Submitted	Last Update

0016825	MMW 5	Sync	public	2020-07-15 22:09	2020-12-18 01:49

Reporter	peke	Assigned To
Priority	urgent	Severity	tweak	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	5.0
Target Version	5.0	Fixed in Version	5.0

Summary	0016825: Device Options: Profile Manage settings can Miss Device Image
Description	If Device profile is imported from MM4 or MM5.Db is moved to another PC or if Install folder is changes then old Device images are not found and shows Invalid Image. Expected is that MM5 tries to find image under same name inside current Plugins\DeviceImages folder or show default device image.
Steps To Reproduce	1. Install MM5 Portable to c:\MMTemp1 2. Create one device profile that have Image (Device image would point to c:\MMTemp1\Plugins\DeviceImages\) 3. Install MM5 Portable to c:\MMTemp2 4. Copy c:\MMTemp1\Portable\MM5.DB -> c:\MMTemp2\Portable\MM5.DB 5. Delete c:\MMTemp1\ installation 6. Start c:\MMTemp2\MediaMonkey.exe 7. Check Device profile Image and it will show invalid picture
Tags	No tags attached.
Attached Files	bug16825.jpg (86,521 bytes) bug16825.jpg (86,521 bytes)

Fixed in build	2262

Ludek 2020-07-20 11:21 developer ~0059035	Fixed in 2262

peke 2020-07-31 01:23 developer ~0059195	Reopen Still not fully fixed If custom Image is loaded and then became unavailable it show as invalid, but it should be reverted to default eg. 1. Assign any Device image using browse 2. Apply 3. Close MM 4. Delete assigned file from Step 1 5. Start MM 6. Invalid image shown

Ludek 2020-08-03 11:37 developer ~0059210 Last edited: 2020-08-03 11:38	Yes, if there is a custom image (with custom filename) and is inaccessible / no longer exists then MM5: - shows only the device icon on the summary page - shows broken link on the [Sync Profile > Manage Settings] page so that user is aware that the image is not accessible and can correct it. For the default images it auto-lookups them in the install folder and uses them when exists (this was the fix in 2262 for the original steps to repro)

peke 2020-12-18 01:49 developer ~0060899	Re verified 2286 Original issue fixed, further improvements if needed should be added post 5.0 release