0000417: Replace the previous default setting "Replace current project" with "Create new resource only".

ID	Project	Category	View Status	Date Submitted	Last Update

0000417	Cinelerra-GG	[All Projects] Bug	public	2020-04-21 02:23	2020-04-21 07:40

Reporter	Sam	Assigned To
Priority	high	Severity	tweak	Reproducibility	always
Status	new	Resolution	open
Product Version
Target Version		Fixed in Version

Summary	0000417: Replace the previous default setting "Replace current project" with "Create new resource only".
Description	https://www.cinelerra-gg.org/bugtracker/view.php?id=71#c3234 Just one comment... I won't dwell on it because we're supposed to be discussing Videoscopes... I never use the "Replace current project" option and I don't understand why it exists, let alone why it appears by default after a new installation... I always create new resources, even when I open an existing project. Feeding the timeline from the resource window seems to me the most normal procedure. I also think that this "Replace current project" option is dangerous, especially if it is offered by default. https://www.cinelerra-gg.org/bugtracker/view.php?id=71#c3235 @Pierre I agree with your assessment. Delivering the option "Replace current project" as default setting is not the best choice in my opinion either. I have been annoyed about it so often. I would suggest we open a new ticket, better it would be if "Create new resource only" is default.
Tags	Resources window

Date Modified	Username	Field
2020-04-21 02:23	Sam	New Issue
2020-04-21 02:23	Sam	Tag Attached: Resources window
2020-04-21 07:40	IgorBeg	Note Added: 0003237

IgorBeg 2020-04-21 07:40 reporter ~0003237	My workflow is different from your, I think. I always use "Replace current project" when I open an old project or a project where I am working on. I use "Create new resource only" when I added files in Resources. But, I would like to have an "Open Project" option in Menu because it would have more sense, for me, and avoid mistakes. I wrote in MantisBT https://www.cinelerra-gg.org/bugtracker/view.php?id=179