I'm having some trouble with Xcode. A lot of times I'll just be typing code in, and then something will suddenly happen that screws up how the text displays on the page. Sometimes it will cut off the first characters of some lines. Other times, especially when I'm typing near the bottom (I notice it occurs when it tries to do some autocomplete but I type over it) it will not display the bottom text (like the #end) and won't take anymore text input properly.
If I quit and restart, the file displays properly again until it happens another time. Does anyone have any ideas how to fix this? I just tried reinstalling Xcode, but even after doing that I still have the same problem.
This problem is really annoying because I often have to quit and restart constantly, and sometimes it's scary because it looks like I've lost the code that I've typed in.
A couple of suggestions:
make sure you're using the latest version of Xcode (3.2.1)
rather than quit and restart, try just saving and closing the file's window and then re-open it
The real solution to this problem is close quick help.
Turns out "Quick Help" causes alot of issues with codesense.
If you close it your troubles are gone. It will work fine once you reopen it... for a while. Then it will begin messing up again.
I used to leave quick help up 24/7 so this happened frequently. I have seen other reports of this being the cause on a few other sites. Aven on this very same site. (stackoverflow)
Related
I came across a problem in Visual Studio Enterprise 16.9.6, when editing an sql script the cursor just goes crazy, when I try to select a line in the file or the navigation bar it just selects files from the solution explorer or whatever sidebar is there, even if no sidebar is present, it just makes it impossible to work on them. With any other file this doesn't happen, only sql files.
It's best to show rather than describe:
Even stranger than that is the fact that it only happens on a secondary screen, on the primary screen everyting works fine.
Anyone had this issue? Any advice?
I was able to pinpoint the issue, as my laptop screen is 15,6", a bit small, I had the scale at 125%, whereas the secondary screen was at 100%, putting the primary screen back to 100% makes the problem go away. I imagine that putting the secondary to 125% would also fix it, though I didn't try that.
I decided to leave an answer because I saw some people with the same issue and some bug reports, though none of them was able to find the source of the problem, for that reason I also decided to leave a bug report of my own:
Bug report
Edit: I see "Silverlight -" is in front of my question, which I realize may have something to do with the alphabetical order of my tabs... really Visual Studio 2013 should be in front, anyone know if that can be changed?
I've been using the newer Visual Studio 2013 for about a week now, and I've found some quirks with it. The one that seems to happen the most is when I'm in the XAML editor working on something, suddenly if I go over to the property window I can't enter anything. I'm not running/debugging. I can type stuff in the regular XAML code editor window.
Even stranger, one of the times, I could get the cursors to appear in the fields. I typed a bunch of junk and just one character from what I types appeared. Another time I couldn't enter values into the properties, but I could double click on an event in the events window and create a new event handler. Just a minute ago I had the opposite, where I couldn't double click in the events window.
I think VS 2013 introduced async handling of more things, could it be related to that? Or perhaps because I'm using Silverlight? Right now my only workaround is to restart VS, does anyone have any knowledge about this? Anyone else experienced this?
I'm going to submit a bug report, but it would be a while before there's a patch, so I'm wondering if maybe someone understand the problem better and has a workaround? Or maybe just confirm that this exists and that I'm not crazy/my computer's haunted.
Edit:
I should mention another weird thing that happened two nights ago. I thought it was some how my doing, but I never figured out how I could have managed it without noticing. I was working on a piece of code, went to run after changing a few lines, and suddenly I had a ton of compiler errors. I go over to a user control I haven't touched in hours and suddenly the main LayoutRoot grid is completely empty. Luckily I'd committed to source control, but still...
I found an easy way to deal with this problem. It happens a lot after debugging so what I did was I created a batch file on my desktop containing this line taskkill /f /im XDesProc.exe and I run it every time the properties start misbehaving. Its the quickest way to reload the designer's functionality. I submitted this bug to microsoft they claim it will be included in the next update.
Me and another guy are developing a silverlight app and having the same exact problem. I accidentally found where the bug lies and how to mess with it to allow you to type "very briefly". Apparently this has something to do with tooltips. If you hover over anything in the property window when this bug is happening and allow a tooltip to popup while your cursor is blinking in a field, for the duration that the tooltip is up you can resume typing normal. As soon as the tooltip times out and disappears you can't type. So the only way you can edit or search properties is while a mouse tooltip is floating active. Very unusual. Can't seem to find any kind of tooltip settings in the program and the situation is very hard to find on google because search results assume your talking about programming tooltips. As far as I know we have had this issue since before release candidate. We are currently on official update 1 with the same problem persisting.
I need to debug some JavaScript an' I use Chrome dev tools. I'm a newby in JavaScript (just started to learn a couple of days ago), an' at work I could set breakpoints via the Resources pane. But at home for some reason I can't do this: after the click no breakpoint appeares.
I have Chrome version: 26.0.1410.64 m.
What could be the case?
clicking on the De-Obfuscate Source button (i.e. {}) solved this issue for me.
I'm a fool! haha! breakpoints are set in the Source pane )))
It's been a while, but in version 33.0.1750.146, but my problem was that I was on the Sources pane (I'd call this a tab; it's one of the items at the very top of the window), but I was on the Content scripts tab (on the left hand side). I needed to switch to the Sources tab.
To be clear, there are two sets of Sources tabs; one is within the other.
UPDATE 2016-01-07: Now I'm on 47.0.2526.106. The only thing that worked for me today was to close DevTools and re-open. It was a little finicky. It worked once, then stopped, and I had to close the DevTools and re-open again. I saw #johntrepreneur's answer about closing the browser, but unfortunately I have too many tabs open on too many workspaces, so that's too much of a pain, so I didn't try that, although I have to assume that would work.
Other solutions didn't work for me. Had to close and restart browser to be able to set breakpoints again.
This also happens when there is a JS error in your code.
Some sort of weird built in function in windows 10 i think because I did press a few buttons by accident. Some of my keys even stopped working in certain areas of visual studio. F.e the letter "c" stopped working in the find window.
Mine did this and no solution worked, i pressed alt, windows key and function key a few times and my problem went away.
Fixed as follows: For me, the issue stems from having set up Chrome to interact with operating system files. If you set this up, then the fact is evident from a green dot by the file name. At some point, I could not set a breakpoint in a recently edited file. I fixed this by disconnecting the interaction, as follows: When viewing "sources", above the code, there were some file names listed. Clicking the [x] to make the particular filename go away gave a caution message; I proceeded without saving. After that, I was able to set breakpoints for that file.
I also had this problem. However, once I closed the popup message in my browser, suddenly all my breakpoints that I set in that time appeared. Mental note: Don't set breakpoints while your app is showing a popup.
I couldn't find any direct fix for this problem.
It seems that chrome keeps settings of your site stored somewhere whatever you do to clean it. (I tried removing the folder from workspace, closing et reopening chrome etc... and nothing worked).
A workaround is to change your site's url to make chrome consider it a new site
I've recently upgraded from Xcode 4.3 to 4.4 and I'm about to bash my screen in with frustration.
The problem I'm having is with the code completion. As I type a variable or method name, the completion window pops up with the suggestions like it's supposed to. But if I attempt to use the cursor keys to scroll between the suggestions, the suggestions disappear and the cursor moves in the code, not between the suggestions. If I press enter to accept the default suggestion, it again dismisses the suggestions and inserts a return into the code taking the cursor to the next line.
This doesn't happen every time I attempt code completion, but it does occur more often than not. For a given name I'm trying to complete, it either works or it doesn't (e.g. if I press escape to get the suggestions back, it will disappear just as quickly as the first time it disappeared for that line/name I was trying to complete). When I get to the next line of code, it's a whole new bet whether it will work or not. It seems that the closer to the actual completion of the name I am, the more likely it is to actually work and accept the suggestion or move between the suggestions. Sometimes, if I act quickly enough, I can move the highlighted suggestion one or two lines before the suggestions disappear. I'm aware that if you don't select a suggestion quickly enough that it's supposed to eventually remove the suggestions (on the order of several seconds), but this behavior is not what I'm describing. I'd be VERY happy at this point if I had a single second to actually respond and select a suggestion from the pop-up.
So far I've tried a clean of the project, deleting all of the project's derived data, and restarting xcode. All of which don't seem to affect the behavior. Any ideas? I've searched stackoverflow and google and haven't found any other people reporting this problem ...
Thanks for any ideas,
Will
UPDATE:
After upgrading to the XCode 4.6 release version (and 4.5 somewhere in the middle there), this problem is still present ... and making edits in the left/main editor window is still a work-around.
I am seeing the same with Xcode 4.4.1. It seems to be related to where the completion window pops up. Debugger pane open or closed does not change anything here.
When in the Assistant Editor trying in the right pane the completion windows flickers. Same line of code in the left window works fine. Single editor works, too.
Try upgrading to Xcode 4.4.1. I used to have this problem, but I don't seem to have it after upgrading.
If this doesn't solve the problem, a crude workaround seems to be to put a lot of blank lines at the bottom of each file - the problem seems to occur from frequently when the file is scrolled all the way to the bottom.
There is a fix (at least Xcode 4.6.3): re-create the affected file by deleting it. Now create a new file and copy the content to it and drag it into the project - done. Fixes the issue here. It seems to be tied to certain files.
I have a problem in XCode 4.2 when I have the autosuggest feature turned on. Whenever an autosuggest (autocomplete) pops up, the cursor will jump to the top of the file, to the second character of the first line. This happens regardless of whether or not I select the autosuggest or take any other action. As soon as I turn off the autosuggest feature, this behavior stops happening.
I have turned off all key binding associated with jumping to the top of the page and have deleted all derived data for the project as per some suggestions I have heard, but have not been able to solve the problem.
Anybody have a solution?
I had similar problem Xcode cursor jumped randomly. It was triggered by an editor theme using an italic font. I changed the font to a regular one, and the problem was resolved.
Simple solution (or workaround):
Open Preferences.
Open Fonts & Colors tab.
Select Basic theme.
I got the hint from this page.
Just in case there is a bounty awarded :) let me repeat my "solution" from above: I suggest moving aside your /Developer folder and re-installing Xcode. Simply running the installer w/o removing the old /Developer folder may not replace all the necessary files. Good luck.
I have had a similar problem where the cursor jumped to the top and I couldn't scroll down. I don't know if it is the same problem that you have but there is no real solution. Its just one of Xcode's bugs there are a lot more. Open another file in the project and go back to the file you were working on, close and reopen the project or restart Xcode. Thats the only solutions I found.
If thats not working, then you can always re-install Xcode