User forums > Help
C::B & Uniwin
thomas:
You cannot turn it off. (You could modify the sources, but I won't help on this because it is madness).
This is a feature that ensures that no matter what happens, you never lose all your data (even if you pull the plug while saving files). As such, it cannot and should not be turned off.
Also, it should do something different: it creates a temporary file, writes to it, renames the old file, renames the temporary file, and deletes the old file after a grace period.
The behaviour that you describe is what wxTempFile does, but we don't use that any more, unless we have forgotten to change it somewhere. It is unsafe because it can delete both files under certain (although unlikely) conditions.
Rigel:
It seems Uniwin support totally broken.
No integrated remote develop in C::B...
But there is some scripting way to implement it...
I trying to do it with batch files, but stuck with setting enviroment variables right before build commands. Trying to "set REMOTE=bla.blabla.com" in Project>Build options>Commands>Pre-build steps fails to execute. Why?
Also there is trouble with backslashes. C::B forcefully replaces slashes with backslashes in Project>Build options>Directories>Compiler.
How can I avoid it?
PS: OS Windows
MortenMacFly:
--- Quote from: Rigel on November 21, 2006, 01:26:00 pm ---I trying to do it with batch files, but stuck with setting enviroment variables right before build commands. Trying to "set REMOTE=bla.blabla.com" in Project>Build options>Commands>Pre-build steps fails to execute. Why?
--- End quote ---
...because the set is issued in another context?! ;-)
Anyway: There is a plugin that does the job for such purposes: EnvVars (Environment variables plugin) - there you can setup/change environment variables in the focus of C::B and it's sub-processes.
With regards, Morten.
Rigel:
I know about this plugin, but it useless for me because in current case i need to set diffrent enviroment variables for each target...
I currently developing client-server crossplatform application. Nightly's broken uniwin compatiblity completely confuses me... Rolled back to 08.11.2006 nightly...
MortenMacFly:
--- Quote from: Rigel on November 21, 2006, 08:49:07 pm ---I currently developing client-server crossplatform application. Nightly's broken uniwin compatiblity completely confuses me... Rolled back to 08.11.2006 nightly...
--- End quote ---
Ok, so we can make a deal: You explain to me how to attach uniwin to C::B (which I will then transfer into a WiKi article) and I'll look into it. It shouldn't be too hard to compare the sources of Now08 with the ones of today to track down that issue...
With regards, Morten.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version