On May 29, 2014, at 7:57 PM, Graeme Costin wrote:
Hi Alex,
You are not the only programmer to experience this. I experience similar useless behaviour in Xcode 5.x with SVN.
The latest crazy behaviour was with Xcode 5.1.1 after I noticed that the Update button was enabled as soon as the compare files dialog opened but, while I was reading the details, the Update button became greyed out!
So I cancelled and repeated the update but this time I immediately clicked on the update button without reading anything in the compare files dialog and the update went ahead OK.
Fine, except that this means I don't get the option of choosing which bits should take the left hand possibility and which bits should take the right hand possibility.
As you have said, this is a crazy bug in the UI of Xcode 5.x!
Overall I like the UI for SVN in Xcode 5.1.1 EXCEPT for this stupid bug which drastically reduces its usability!
All the best,
Graeme
Thanks Graeme. What worked for me was waiting N+1 minutes.
What I've also seen, which scares me is when checking "History", I sometimes see nothing at all. When I do see something (even after Updating History), I'll see commit \notes from last week.
Today, I synched down the 20 or so files that were updated in the repo for the whole workspace, but when I checked history to see my other team member's commit notes, for what was updated, all I saw were at first nothing, then after canceling and checking again, the commit notes that I had entered last Friday.
Then Xcode crashed on me while attempting to draw a view. (At home now, don't have the crash log in front of me.)
It's times like that when you think "I'd love to report all of these, but I'm not paid to enter bugs all day in someone else's product" and you wonder if anyone ever tested this section of the product - which is rather important.
What amazed me was when testing out SVN support, before we moved into it completely form Perforce, was that when hosting the repo on my own box using SVNServe 1.7.10, how simply adding a file or files would instantly crash the SVN version of Xcode 100% of the time in line 1519, while trying to access a URILocator (or something to that effect).
Sure, I'd love to write this one up (and I am), but the time to write up a bug so that it's not a waste of the developer's time is not trivial.
We're on version 5 now and we have these issues. I want to know what possessed the GUI team to completely redo the UI (which takes valuable developer resources), make it glaring white, remove important context and value that development effort over NOT REDOING THE WHOLE UI FOR THE ENTIRE PRODUCT, and actually fixing the bugs that are already in the product.
Actually removing the alternating row colors in many areas of Xcode, putting development into actually doing this, makes the UI HARDER TO UNDERSTAND and takes dev time away from THINGS THAT WOULD BE CONSTRUCTIVE, like fixing ever present bugs in the system.
It boggles my mind why the team was told that the product needed a reskin and that priority was placed higher than fixing bugs and leaving a good looking UI (that worked) alone.
I've spent way too much time in the past few weeks dealing with this non-responsive source code UI and guessing what Xcode is doing in the background, as well as getting completely inconsistent results from History.
It's not inspiring confidence and certainly doesn't indicate a stable product when the source code control is a guessing game.
My Director can fork out a purchase for Versions for himself - and has. The rest of the team sits and swears at Xcode every time they have to update or commit to SVN.
One guy actually develops on the PC, just so he doesn't have to deal with the commit/update drama the rest of us are stuck with.
An iOS developer is actually writing his source on the PC just so he doesn't have to deal with how poorly Xcode supports SVN.
That pretty much sums up how bad it is for us.
Fun times.
On 30/05/2014, at 5:50 AM, Alex Zavatone <
email@hidden> wrote:
On May 29, 2014, at 2:26 PM, Marco S Hyman wrote:
5 - 10 minutes to wait for the interface to update WITH NO USER FEEDBACK for a repo update is insane.
Did the update take 5-10 minutes? If so you got your feedback...
No. The update didn't. The window was open with files to compare and nothing for me to do except click Cancel.
6 minutes transpired and the Update button magically enabled.
Now, as my memory refreshes itself, I remember this happening sometime last week and while I was typing an email asking "What is going on?", the Update button magically enabled AND clicked itself while I was typing an email on another computer.
<snip>
Graeme Costin
Costin Computing Services
Ph: 02 9419 7038
Mo: 0416 354 234