User forums > Using Code::Blocks

Feature request for "Reload file ?" requester

<< < (2/3) > >>

dmoore:
Schlumie's issue could arise whether or not he uses SVN. Occasionally a source or other text file that is open within the IDE will be overwritten by another process. It would be useful to be able to quickly figure out what was changed by having the option to pop open the new version in a new tab, rename the old version, and maybe put a diff in yet another tab. currently you have the option to reload or not reload, but not the option to see both.

I can't see this being high priority...

Schlumie:
At last.... someone who understood me  :) ..
The more sophisticated method would be to remember the filetimestamp at loadtime and compare it when saving the file again. If the timestamp has changed, a other user has changed the while while editing... and a popup could warn about it..
The "Reload file?" requester only comes up on application focus change, i think..
I hope that, even if this feature gets no high priority, it will be integrated some time.. 

thomas:
I understood your issue was about being able to see the changes you may have made outside Code::Blocks if the "file has changed" dialog pops up. However, the last post sounds like your intent is to check for modifications every time a file is saved, because two developers work on the same set of original, non-versioned files at the same time.

I don't think this should be implemented in Code::Blocks at all, since it is silly. If you have two users modify the same original source tree concurrently, then honestly, you deserve conflicts.

Use Subversion, that's what it is for! It works reliably with 2 people (or with 2000) working concurrently, and it offers a big deal of other useful functionality (for example having a commit log, or the ability to go back in time, or the ability to track who did what change, branching, ...).
Subversion (or another RCS) is even useful if you work on a project all alone, but for any serious project with more than one developer, it is absolutely mandatory, there is no way around it.

dmoore:
I have to say I'm with Thomas on this one. If two or more of you are simultaneously editing the same source on a network share or something you're asking for trouble.

dje:
Binary build must be very fun and surprising  :D
Do you have to guess what has appeared in your binary ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page