View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011472 | MMA | Synchronization | public | 2013-11-11 15:34 | 2013-12-01 22:28 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0.4 | ||||
| Target Version | 1.0.4 | Fixed in Version | 1.0.4 | ||
| Summary | 0011472: Item selection doesn't work in Auto-sync list | ||||
| Description | There are two reports that selection of items in MMA's auto-sync list doesn't work. In both cases, attempts to select an entry in the list result in the entry flashing, but not getting selected. Could it be that the position of the checkbox isn't being read properly by MMA on screens of certain sizes? | ||||
| Additional Information | ITG-305601 YUK-113807 (this report also includes a video illustrating the problem) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 189 | ||||
|
|
Note: I've tested with a Galaxy S3 and can't replicate this problem, and one of the users was experiencing it on an S3. So it likely isn't related to the screen resolution. |
|
|
Fixed in build 186 It was probably related to new implementation of upnp service. |
|
|
I am thinking about the video the user have posted. He is clicking on the item ... not on the checkbox (when you click on checkbox, the background doesn't blink). We can implement that items that are not browseable can be checked by clicking on the whole item too. What do you think ? It might be less confusing.. |
|
|
I'm not sure that the problem is the fact that he's clicked outside the checkbox (since another user was specific about the fact that he clicked the checkbox). BUT, the solution that you suggest would work, and would even be an improvement in usability, I think. |
|
|
Fixed in build 189 Please note that I observe that my network is so laggy that it takes approximately 10 seconds to get answer from MMW. It was already described and agreed before in 0011073 . When user checks, it is checked immediately, but he cannot immediately uncheck it in such bat network condition. He can uncheck it after response on check from server arrives. This is I think ok. Most of time it is quick enough. Issues in build 182-185 were caused by incorrect changes in upnp service. But it was already fixed. In build 186, I reverted it to state in build 182 and now I've just added checking on clicking on container. |
|
|
Verified 189. |
