sexta-feira, 23 de maio de 2008 21:53Here's the scenario -
- A file in a folder that has been shared with a second member is opened by both members simultaneously.
- Whether or not either member modified and then saved the file, a file conflict is created.
- In the resolution dialog, two versions of the file are listed.
- One option is to "Keep ..." one of the files. Problem - you can only "Keep" the first file listed. If the second file in the list is selected, the "Keep" button is grayed out. Huh?
- The second option is to select one of the versions and "Save as", presumably leaving the other one as the sole version, therefore fixing the conflict. Problem - selecting one of the files and "saving as" doesn't resolve the conflict. Both files are still listed.
Related suggestion -
When a file has been shared to facilitate collaboration, it would be really nice if there was an easy way to see that the file was in use by the other member. Perhaps a "read only" message, a note in the News panel, a colored icon/filename - most anything that is an unmistakable visual cue that, if you open the file, a conflict is going to occur.
PS - Why is it necessary to declare a "conflict" when the file has not been modified/saved?
- Tipo Alterado Ben [Live Mesh] sexta-feira, 23 de maio de 2008 22:52 Edit for Answer
Todas as Respostas
sexta-feira, 23 de maio de 2008 22:51Hi mcgumic,
We are certainly working to improve how Live Mesh handles and reports file conflicts, but would you mind submitting a bug report and attaching your logs so that we can take a closer look at this particular case?
Also, if you'd could add your related suggestion to our Wish List sticky thread, I'd appreciate it - that's where we are keeping track of all the great suggestions coming in through the forums.
Finally, in answer to your PS question: There are cases where a file is changed even though the user did not modify/save it, e.g., Word will update a docx file on open if it is protected by DRM. It is certainly possible, though, that your experience in this regard is part of the bug you're encountering, so again a bug report with logs would help us greatly.
To submit a bug report with logs:
Please go to http://connect.microsoft.com/. Sign in and then select Live Mesh Tech Preview on Your Dashboard. Click Feedback and follow the instructions for collecting your logs and then submit a bug.
To get your logs:
1. Click Start.
2. Select All Programs and look for the Live Mesh folder.
3. Click Collect Live Mesh Logs.
4. Your logs will be bundled together in a cab file now located on your desktop.
Attach your LiveMeshLogs.cab file located on your desktop to your bug.
Note: you will have to submit a bug first, then edit it to attach your logs.
If you do not have access to the Live Mesh Connect site, you can email your logs to firstname.lastname@example.org. Please provide as much information about your issue as you can in that email.
- Editado Ben [Live Mesh] quarta-feira, 28 de maio de 2008 19:57 font