Code::Blocks Forums
User forums => Help => Topic started by: killerbot on June 29, 2006, 11:14:59 pm
-
Should for "save all files" also the project file and the workspace be saved ??
(currently : it's only the source files)
yes/no ?
-
Not seriously?
-
I would say yes.
-
Should for "save all files" also the project file and the workspace be saved ??
(currently : it's only the source files)
yes/no ?
That would put me in serious trouble. I make test build options changes etc that I do not want saved when I save a file.
What if you ctrl-z your changes to files? You can't undo a project file.
Then when you save... oops too late... Do I remember what changes I make?
With my "senior moments", most likely not.
But we could always add the option to the context popups.
-
Again: not seriously? :lol:
That would mean that the project is saved every time you compile... so if you make a build with optimisations turned on, it will save that to disk!
-
Hell no.
-
A no here .o/
-
some clarifications :
- save 1 (source) file -> does not mean saving the project file
- internal "save all calls" (eg because of compile (regular or a build with a different optimizations) -> "hell no" ;-)
It's for the case where the user explicitly asks (button or menu) : CB, please save all my files.
-
Using the menu option Save All -> Yes
When compiling or saving just 1 file -> "hell no" :P
-
Even when selecting "save all files", it is wrong and problematic.
Although it is technically true that project and workspace are eventually saved to files for permanent storage, insisting on "but they are files" is nothing but a pedantism.
The project holds the project's files, it is not one of them. I don't know of any software that handles this differently (and no, I am not interested in an example, don't bother searching).
One might equally argue whether "save project" means "save the project, including all source files" or simply "save the project file". After all, "the project" is the project file plus all source files. A project file alone is nothing without the sources, so if you want to be consequent, you must save those too. However, I guess that none of you seriously expects this to happen.
-
I think we could agree upon the fact that we won't save the project and workspace files on "save all". So it will not be considered as a bug.
@Thomas :
- no need to search for examples, I know some ;-)
- does your autosave (which creates backup copies ??) save the project/workspace (since maybe I did change some project settings to be permanent and woops crash ... :-( )
-
No (http://forum.tgmonline.it/forum/images/smiley_icons/nono.gif)
(poll?)
You could make a "save all files project workspaces" new menu item, if someone really want that.
-
A resounding "NO!".
Thomas has explained it well.
For any projects other than "Hello world", saving the actual project file should be the developer's choice when to happen, not the IDE's...
-
does your autosave (which creates backup copies ??) save the project/workspace
Autosave does what you tell it to do, not more not less :)
If you tell it "save the project" then it will save the project. Otherwise it will not. If you tell it "overwrite" or "create backup" then it will overwrite the original (and optionally create a backup copy first), but if you leave the default "save to '.save' file", then it will save to ProjectName.cbp.save and leave the original untouched.
If you tell it to save the sources, it will do just that, and leave the project untouched.
-
Strongly recommends you implement this...
Strongly recommends you implement this...
Strongly recommends you implement this...
Strongly recommends you implement this...
:lol:(Just kidding^)
:o What do you mean not funny?