UI dirtiness not triggered for table edits
Submitted by Khumba
Assigned to Brasero maintainer(s)
Link to original bug (#746726)
Description
Editing the names of files in a data project, and changing the names of tracks in an audio project, don't trigger dirtiness which would allow saving, and at least in the data case, these changes also doesn't make it to the CD when burned. If someone makes last-minute changes to file names or placements before burning, these changes will be lost.
An example:
- Make sure you don't have blank media in your drives.
- echo foo >/tmp/foo && echo bar >/tmp/bar
- Open Brasero and create a new data project.
- Add /tmp/{foo,bar} to the project.
- Save the project, say in /tmp/cd.
- Create a new folder ("New folder") in the project.
- Dirtiness is triggered, so do a Project -> Save again.
- At this point, the folder isn't mentioned in /tmp/cd! (Separate issue?)
- Drag the project's foo and bar into the folder.
- Project isn't dirty; can't save!
- Click Burn to burn an iso, and inspect it's contents.
- The iso mirrors /tmp/cd, as though burnt after step #4.
- Back in the project view, rename foo or bar and create another iso.
- Same result as the previous step.
The same goes for editing a track name on an audio CD, although I didn't test burning an audio CD in this state.
A workaround is to modify the disc title field before saving and burning.
Observed on 3.12.0 (Gentoo) and 3.10.0 (Linux Mint 17.1). Closest bug I could find is #744931.