#52 Refresh Problem

closed-fixed
nobody
5
2012-09-11
2010-04-13
kakusi
No

With following steps, we can reproduce our problem:
1. developer 1: open resource files with rbEditor and select one entity
2. developer 2: add new entity to the same resource file and check in
3. developer 1: update the resource files (wich won't change the first view (summary view))
4. developer 1: add new entity using the summary view and check in
Result: developer 1 added its own entity and implicit deleted the new entity from developer 2

Ok, we understand this and always reopen rbEditor after updating files. But it would be nice, if it would not be necessary.

Discussion

  • We face the same problem.
    It is very annoying always need to remember reopen rbEditor after updating files.
    If someone forgets that, then afterwards easily stale versions get commited on the source code repository
    which could create big troubles.
    At least if the Update-action is performed through Eclipse itself, then the rbEditor should not ignore it,
    that would be nice.

     
  • Cuhiodtick
    Cuhiodtick
    2012-09-11

    • status: open --> closed-fixed
     
  • Cuhiodtick
    Cuhiodtick
    2012-09-11

    Thanks for the bug report. Fixed in 0.8.0