Bug report #20743

After handling bad layers, no unsaved state

Added by Nathan Saylor over 1 year ago. Updated over 1 year ago.

Status:Closed
Priority:Normal
Assignee:Alessandro Pasotti
Category:Project Loading/Saving
Affected QGIS version:3.4.2 Regression?:No
Operating System:Win7 Easy fix?:No
Pull Request or Patch supplied:Yes Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:28563

Description

Sorry if this should be going under feature request, but I think it's problematic.
After handling bad layers, QGIS does not set the project to an unsaved state, so a person could close the project from that point and not have the option to save with the updated layer sources.
Checked in 3.4 and 3.5 (Which thank you for the options to hang onto bad layers in 3.5. That's a feature I've wanted for a long time! :) )

Associated revisions

Revision 0042cc0f
Added by Alessandro Pasotti over 1 year ago

Mark project dirty when bad layers have changed

Fixes #20743

History

#1 Updated by Alessandro Pasotti over 1 year ago

  • Assignee set to Alessandro Pasotti

#2 Updated by Alessandro Pasotti over 1 year ago

  • Pull Request or Patch supplied changed from No to Yes

#3 Updated by Alessandro Pasotti over 1 year ago

  • Status changed from Open to In Progress

#4 Updated by Alessandro Pasotti over 1 year ago

  • % Done changed from 0 to 100
  • Status changed from In Progress to Closed

Also available in: Atom PDF