Project

General

Profile

Bug #1887

Kepler: unsaved changes management policy is not natural

Added by Anonymous almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
01/13/2014
Due date:
% Done:

100%

Estimated time:

Description

SITUATION: a change is made in any editor

PROBLEM: closing any editor (even another than the one where the change happened) triggers a "There are unsaved changes, do you want to save them?" dialog

-> This is really annoying and counter-intuitive because the closed editor has nothing to do with the change

History

#1 Updated by Anonymous over 6 years ago

  • Target version changed from Phoenix - BACKLOG to Phoenix 2.6 Release

#2 Updated by Anonymous over 6 years ago

  • Target version changed from Phoenix 2.6 Release to AF3 2.6 RC2 Kepler bug fixes

#3 Updated by Georgeta Igna over 6 years ago

  • Assignee set to Georgeta Igna

#4 Updated by Andreas Bayha over 6 years ago

  • Status changed from New to Closed
  • Assignee deleted (Georgeta Igna)
  • % Done changed from 0 to 100

The issue actually was an internal problem of eclipse which is resolved in newer versions of Kepler...

#5 Updated by Anonymous over 6 years ago

So, to make it clear: this is simply solved by updating your Kepler install

Also available in: Atom PDF