The resizing of the different Panes/Windows in Xcode often stops working and I have to toggle hide or show in order to reactivate it.
If you look at the images below, sometime I cannot get a resize cursor as shown in the second image.
I have been patient. I keep expecting the next version of XCode to solve this bug or maybe the next OSx.
I am now on Xcode 7.1.1 and OSx 10.11.1.
Am I the only one who has the recurrent bug ? Is there a fix anyone knows of ? I always click on one of the toggles switches in the toolbars and it fixes it but I cannot stop it reoccurring.
In my experience this has never caused Xcode to freeze, but also you can resize the panes regardless of whether the cursor changes or not. Just point to that area and drag it - it will follow.
Is it just me, or does this happen to anyone else? Occasionally if I am coding inside of a huge class, the source code text begins to chop it's way out to a white screen as I scroll. However, when I vigorously scroll to the top, then back down again. The source code re-appears again.
What could be the issue? Is there a work around? This issue is so annoying!
Go to Preferences->General tab and uncheck "Show live issues" under Issues. Notice that this is a work around to be able to continue working with Xcode, at least until they issue an official fix. This glitch seems to be noticeable when you have lots of lines of code (1000+).
After this, the glitch will still be happening but not while coding but during building phase. Not perfect but at least you will be able to continue working.
I am trying to work with storyboards in iOS, and it's driving me nuts because I can't drag storyboard elements around in the UI to clean up the visual structure of the relationships. Should I be able to move them around? If so, what might I be doing wrong?
I should note I am accessing the Mac environment via RealVNC on Windows, which might have something to do with it, and I have little choice in the matter, unfortunately. But I have no problems moving UI elements around within a view. It's just the top-level storyboard views that I can't rearrange.
EDIT: I've dropped the storyboard tag, since this seems to affect all top-level views and windows in my Xcode editor, not just those belonging to storyboards.
I ran into this problem using a Synergy client on a mac. I assume it has something to do with the mouse lag and how the storyboard registers click and drag. My solution for now is to use a mouse connected directly to the mac, but it would be nice if the Apple would fix this issue in future xcode releases.
I was facing this, I have a magic trackpad, and as it turns out if you point your mouse on the battery symbol in the storyboard and try to move them, you can do it very easily! :) (not sure if this is a known thing, just adding it here, if somebody has the same question since google's first hit is this one)
EDIT: Well you can just drag it around using the controller bar below the storyboard so this answer is a little late, but now there are two ways. :)
After trying almost every remote screen implementation I could get my hands on, I've come to the same conclusion.
This also affects control-drag for connections. The workaround on ctrl-drag is to right click on an element and drag from the pop-up menu.
For dragging top-level elements, I have a spare mouse connected to the mac like you. But this fix isn't robust because if the mac (running VNC) doesn't have a monitor attached, the remote cursor does not seem to report itself to VNC clients correctly. Is this consistent with your findings, or does your mac have a monitor connected? Reboot with a monitor and I suspect your mac-mouse will not behave correctly through VNC. The fix here is to connect a monitor to the mac briefly, and then remote cursor reports itself correctly from that point onwards (until the next reboot).
I just bumped into the same issue, I was using Synergy v. 1.3.7 on Mac (Client) and Synergy v. 1.4.4 on Linux (Server).
I upgraded to Synergy 1.4.10 on both Mac and Linux and now everything works for me as expected.
I am using teamviewer from my windows desktop to connect to my macbook and have the same problem.
I couldn't solve it on my desktop anyways, you have to make these changes in mac.
As a partial solution when using Google remote desktop:
Drag a new item from the Object library. This is working normally until you drop the item. Afterwards you can't drag the item again.
Open the outline view. See picture at https://developer.apple.com/library/content/referencelibrary/GettingStarted/DevelopiOSAppsSwift/Art/2_outlineview_toggle_2x.png
Than drag the item from there. You can drag it and when dropped, the original item will be moved to the correct place. The problem with that is no help lines are presented in order to align the item and no accurate position can be done.
Use the Size inspector. See pic at https://koenig-media.raywenderlich.com/uploads/2015/11/46_vc_size-e1448290482977-421x320.png
From there you can set the correct size and position of the item.
I'm using a Mac in a VMWare Virtual Machine through VNC from Windows, same problem. However, logging in to VSphere directly, and opening a console on the VM does let you move elements and control-drag.
This requires access to VSphere, though, which your System Administrator may be reluctant to provide.
I was using ShareMouse 3.0.35 for sharing mouse and keyboard between a PC and a MAC and when I turn it off, I can drag things around on the storyboard. Posting this to assist others. Of course, now I have to push my manual KVM which is a drag (pun intended)
I'm experiencing this on WMware player 14 and macOS 10.13 with Xcode 9. The only workaround I've found is under the pane with the vertical ruler icon, in the section called View, and manually adjusting the X and Y coordinates
I have a TTLauncherView in my ios app. I have allowed users to edit and move their items around, however it does not appear that you can move the item from one screen to another, does anyone know how to do this?
that's looks like another a bug in three20 library. I just checked an old app of mine and moving items from page to page works fine. It means it might be another iOS 5 issue.
You can open a bug for it in http://github.com/facebook/three20, hopefully someone will fix it.
If I'll get around to it, i'll check it and fix it. I have a few apps using it, so I might need to do that.
I experienced a similar problem. It seems to be a bug just for the first icon on that page (i.e. creating a new page) - adding just add another icon to that page works fine (at least for me).
You can get around this bug by dragging the icon to the new page and releasing it on the first row (on the top of the page!). This isn't really satisfying, but perhaps a good starting point.
I have a user who cannot bring up the keyboard when she taps in the textfield of my iPad app. There are over 100 users who have no trouble doing this, and I cannot find a way to reproduce her problem (I've observed everything working correctly on 12 different devices). She insists that she has tapped in the text field and that nothing happens. Has anyone experienced a similar issue?
I welcome your thoughts on this one. Thanks!
UPDATE: Another user has just reported a similar problem. While initially I thought this may be a PEBKAC, but since two independent people are having the same issue, that is becoming less likely.
Does she have long fingernails? Does she tap with her index finger, but allow her middle finger to touch the screen at the same time? Does she drag a bit when she taps?
Can somebody else using her device get the keyboard to appear?
I wouldn't consider it a code problem until you eliminate user error.
If it is a code problem, check that some other view isn't overlapping your textfield and intercepting touches.
Does she have a Bluetooth keyboard connected?
From one of the users:
I updated the software from 3.2.2 to
the latest version 4.1.1 and did a
firmware update. The app works fine
now!
Odd, since I back tested it, but at least the problem is resolved at last.
UPDATE: The second user also confirms that this solution worked. I'd love to hear if anyone else experienced similar issues.