User forums > Nightly builds
The 27 February 2010 build (6181) is out.
filofel:
--- Quote ---OK, Live with the crashes... You can't be helped
--- End quote ---
PMJI, but that's a problem I've been experiencing too:
When C::B abruptly terminates for any reason (might not even be C::B fault), most of the time, a part of the project is lost. Or at least, the latest modifications are lost (such as files recently appened to the project, etc.).
It would be nice if anything that is saved in the config would be written to disk and flush() committed immediately, to minimize the risk of ending up with an obsolete and/or corrupted config file. I think that this is what Critic meant.
C::B crashes very rarely under me (even though I'm running bleeding edge nigthly builds, 6203 as of today, courtesy of Jens Lody's repositories, mucho thanks Jens).
But in the rare occasions when I had a problem, I ended up with missing items in my project. Even though I have Autosave set to 4 mn on both sources and project, BTW.
I guess this can be simulated quite easily by abruptly ending the C::B process. :)
MortenMacFly:
--- Quote from: filofel on April 13, 2010, 05:15:55 pm ---It would be nice if anything that is saved in the config would be written to disk and flush() committed immediately, to minimize the risk of ending up with an obsolete and/or corrupted config file. I think that this is what Critic meant.
--- End quote ---
Look: This would make it impossible to play with project configurations e.g. for optimisations. I personally do that quite often but if this would be saved every time I would always need to revert it back. I don't agree that this makes sense. The same would be that every time you are typing a character in the editor the editor shall be saved. This makes no sense.
The only solution I see is to adapt the autosave plugin to save project files in a certain interval, too. This can be toggled and is convenient.
--- Quote from: filofel on April 13, 2010, 05:15:55 pm ---I guess this can be simulated quite easily by abruptly ending the C::B process. :)
--- End quote ---
Same thing here: Did you ever think when I kill a process I want exactly not to save anything?
filofel:
<shrug>
I've been using *alot* of IDEs, and I've never experienced that kind of behavior before.
IOW, all those I know of do secure config modifications either instantly or at validation time.
--- Quote ---The same would be that every time you are typing a character in the editor the editor shall be saved.
--- End quote ---
The comparison doesn't hold, IMO. Typical use case doesn't show the same change rate, by several orders of magnitude. And the config changes tend to be more important because they impact the whole project, and update losses are not proofed by a compiler.
--- Quote ---Same thing here: Did you ever think when I kill a process I want exactly not to save anything?
--- End quote ---
If you consider killing C::B as a "normal" way to exit it (like a "quit without saving" menu item), then you are probably right. But as far as I'm concerned, I've never had to kill C::B (or any other IDE) for such a reason.
It looks to me the motivations you mention are more those of a developer of C::B who needs this behavior for testing C::B more conveniently than those of a vanilla user of C::B using it for developping anything else.
Nevermind...
critic:
Please, note that: sometimes at development process I add global variables or change them and when I close `global variables` dialog I expect they will be saved at that moment, but they don't. I think this example shows that behaviour of IDE in such situations is strange.
oBFusCATed:
--- Quote from: filofel on April 15, 2010, 08:23:07 am ---<shrug>
I've been using *alot* of IDEs, and I've never experienced that kind of behavior before.
--- End quote ---
Please name some of them? Visual studio isn't doing it (all versions <=2005, don't know for newer ones).
I've not tested other IDEs in years.
If the Save on OK is implemented, what would be the behavior when there are two instances of C::B?
The second instance should detect the configuration change and then what?
To all: please keep in mind that when one software crashes this is a critical bug. It should be reported and fixed.
And developers fix crashes they know about...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version