View Issue Details

IDProjectCategoryView StatusLast Update
0010257MMASynchronizationpublic2013-01-14 02:17
Reporterrusty Assigned To 
PriorityimmediateSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.0.1 
Target Version1.0.1Fixed in Version1.0.1 
Summary0010257: Facilitate installation of MMW server if not installed
DescriptionIf MMW isn't detected, upon an attempted sync operation, this may be because:
- MM isn't running
- The wrong version of MM is running
- Network problems

Currently, if no sync server has been configured, MMW shows '<Searching...>', and once a timeout occurs, gives the user the ability to e-mail a link to download the server?

If a sync server has been configured, then MMW shows:
Waiting for the remote server... If this is your first time connecting to it, you'll need to accept the connection on the server in order to proceed. [Cancel]"


We should modify the messages (most importantly if no sync server is configured) so that they describe how to install the correct version of MM. e.g.
1) In the case of a timeout while '<Searching...>', there seems to be a bug as a timeout never occurs. Should a timeout occur the message should be presented in a manner similar to case 2 below.

2) In the case of a sync server that has been configured:
Waiting for the remote server... If this is your first time connecting to it, you'll need to accept the connection on the server in order to proceed. If you haven't yet installed a MediaMonkey sync server, it can be downloaded via: http://www.mediamonkey.com/android/10/server
[Cancel] [e-mail link to self]

As described at 0008705:0032750, the various portions of the message shouldn't always be displayed (e.g. if a server is detected, but it's taking time to connect, the last sentence needn't be shown.

Note: in the case of the first message,
TagsNo tags attached.
Fixed in build88

Relationships

related to 0008705 closedjiri MMA Synchronization UI 
related to 0010197 closedmarek MMA Connection message is redundant 

Activities

marek

2012-12-22 17:15

developer   ~0034138

Fixed in build 88

peke

2013-01-14 02:17

developer   ~0034409

Verified 92