Thanks in advance,
Perhaps you should read the manual then? Basic Work Cycle. Any work you start, should start with an svn update to ensure your working copy is up to date. Prior to a commit you should do an svn update to make sure you have the latest changes merged in and conflicts resolved prior to attempting a comit.websnail wrote: I must admit I don't recognise "update" as a SVN command at all so I'm a bit confused as to why you would think it's the norm...
Well...Anyways... Tortoise SVN provides a slew more functionality than the current UEStudio function set and is exactly what you need should anything go awry with your SVN working directories.. That and the help files will help clarify information relating to SVN where the current UES help docs are very much lacking...
To expand on this point: don't use Subversion support as a decision criterion for purchasing or upgrading to UEStudio. UEStudio supports Subversion as long as you're going forward. IDM ignores the concept that one of the great things about version control is the ability to easily examine where you've been, return to a working version after messing things up, and resolve conflicts between multiple contributors. Specifically:THEMike wrote:The point of UES is that it's an IDE, thats Integrated Development Enviroment. If you de-integrate the version control, then you have a DDE, Deintegrated Development Environment.
The essential point of an IDE is that you have one interface to do all your development tasks. If the IDE doesn't do that, then just use a set of best of breed applications, which would mean UES wasn't the tool for you, you may as well stick to UE and save the upgrade fee.
For others having trouble with this, the fix for Windows is fairly easy. Download the latest subversion command-line client from subversion.tigris.org. Find UEStudio's installation directory. Inside that, you'll find a directory called GNU\subversion. Install the new subversion into this directory, overwriting the files that installed with UEStudio. You'll then be able to perform subversion operations from within UEStudio.1. The Subversion support is out of date by a year (1.5.2, not 1.6.1 which is current)
Yeah, the loss of the status icons is not a trivial problem, because UEStudio uses the status to determine what you can do with a file via right-click. Once you update the subversion client (so that you can do anything at all), all you can do with individual files is Add.3. The poor implimentation means that you can import and update from repositories and it will "try" to work with it but you don't get icons showing status of any files.
It's funny you should mention that, because that's how I do it, too! However, I have learned, by trial and error, how to set it up with the UEStudio interface. Completely avoid the "module manager," and note the "Gotchas" in italics: There's an "Accounts/Settings" item that makes everything go more smoothly. Go there and click "Add Account," and enter the protocol (e.g., "svn"), host, username, and repository. Put a / at the beginning of the Repository field, otherwise UEStudio uses the wrong host. Don't bother filling out the password, because you'll be asked for it again anyway.4. I haven't worked out how you setup a VCS module from scratch because the documentation is so utterly lacking. The only working method is to checkout a module in windows explorer using tortoiseSVN (or similar) and then add a folder to your project and hope that you get the Import VCS settings dialogue.