Running Analyze in Xcode 4.0.2 shows issues in the Issue Navigator. Clicking on an issue makes the appropriate file appear in the Editor pane, but nowhere does it show where in the code the issue occurs as I am used to from Xcode 3.x. Does anyone know how I can turn on this feature?
A couple of tips:
First, if you're looking for the view where Xcode annotates the project with arrows, bear in mind that you may need to expand the top-level analyser result in Xcode's Issue navigator and click the second-level issue in order to see those - see screenshots.
Screenshot 1: top-level issue selected - no arrows
Screenshot 2: second-level issue selected - arrows!
Second tip: if that stuff isn't working, try cleaning the project's build products folder. Hold down the Option (alt) key and choose Clean Build Folder... from the Product menu. (You need to hold down the Option key, otherwise you won't see that menu option.)
I've seen this happen before sometimes. I believe it's a bug in Xcode. Restart Xcode and try again.
One note. I'm seeing this for files that are referenced outside the current project. I currently have a library in which the files with missing annotations live and simply added them to my current project without copying them. Haven't done the project dependency setup yet, so if you're referring to files outside your project that could be why. (I opened the library project, did an analyze and the annotations showed up.)
Woohoo, I've nailed it! At least for me. I've been struggling with this problem for about 2 hours now, trying out all the things suggested here and more (Xcode 4.0.2, Snow Leopard). Bizarre thing was I had one file where the warning were correctly showing in the editor. Then I noticed the difference to all other files; in the File Inspector pane the location was specified as "Relative to Project" (warnings show correctly in the editor), all the other project files were "Relative to Group" (warnings not showing in the editor).
I took one of the problem files, switched it's location to "Relative to Project", reanalyzed and bingo! I've see it's warnings in the editor.
I guess this ties in a bit with David Goodine's answer refering to files outside the project.
Related
So I recently moved all of the files that I want to keep onto a secondary hard drive in my laptop. This also included the workspace I use for Aptana Studio 3. As a result, there was a particular file that I had to delete and let the program recreate just to get the program to start up as well as re-import the projects I was working with.
The issue now, though, is that I cannot change or even bring up the themes in the preferences editor. When I first go to Window > Preferences > Aptana Studio > Themes, I get a message that reads:
The currently displayed page contains invalid values.
and doesn't show anything. On the rare occurrences that I AM able to get that particular window to show up, there's nothing there except an empty drop down menu. Anyone have any ideas on how to correct this? Thanks.
P.S. YES, I have Googled it and hence, since I didn't find anything, I'm asking the question here.
got this answer from another post...
I got the same problem. After updating Aptana to 3.5, whenever I looked at the themes settings, it crashed down saying.
"the currently displayed page contains invalid values"
Probably the new update has its own bugs for some reason.
the only way to fix the problem is to downgrade the version of Aptana studio.
https://wiki.appcelerator.org/display/tis/Reverting+to+a+Previous+Version#RevertingtoaPreviousVersion-AptanaStudio3.4.1
just Download 3.4.1 version and all things gonna be ok.
Add Eclipse Themes from http://eclipsecolorthemes.org/?view=plugin
Details to add themes on this post.
Edit: This does not seem to work :( only the bg changes. I never noticed that the font colors never changed. Have to wait for patches I guess. Don't want to downgrade though :-|
I'm using the Brackets editor, and I ran into this extension.
If you look at the picture on this extension's page you can see the small light bulbs next to some lines. I really want this feature, so I've installed the extension, but I can't see those light bulbs.
Is it a part of this extension or is it another extension in this picture?
If so, which one is it?
Those icons come from the Brackets Interactive Linter extension, created by the same author. However, they don't give you "auto correct" options like the lightbulbs in some other editors. As far as I can tell, the icon just shows you more details about the linting error.
If "auto correct" is what you're looking for, you might still be able to interest someone in working on that functionality. (The Brackets community is pretty responsive!). I suggest:
File an issue in the extension's repo asking for the enhancement; or
Start a thread on the brackets-dev forum making this suggestion, in case any other extension developers would be interested in working on it.
If you are using AEM Brackets Extension and are unable to install the extension via url then either try to drag and drop the .zip into the DragDrop area or add your unzipped extension folder into \www\extensions\default directory and run the brackets tool via cmd line rather than double clicking on it.
It worked for me!!
I've been using Aptana Studio 3 for awhile now and I like it much better than Dreamweaver. However, one quirk that's starting to annoying is that if I have a few scripts/documents open from my project, when I click on one of the open tabs the project explorer automatically jumps and selects that file in the list.
This is very annoying when trying to view a list of files in a directory and also trying to type in a script/document that is located in another directory.
So my question is: How do I get Aptana Studio 3 to not automatically jump to a file like that?
Thanks.
I don't know why this post was voted down. I think people don't like to actually read the FAQ.
I believe your problem is the 'Link with Editor' option in the Project Explorer. You can find it under the little arrow at the top right of the Project Explorer. Make sure it is turned off.
I was about to add a new app icon in Xcode 4.3 when I accidentally clicked something in the project inspector (the joys of using the touchpad and not a mouse). I had my project selected and was about to add a new image for iPhone retina icon when I accidentally selected something and now I cannot see anything of my project. The last thing I remember seeing was a drop-down menu change to "Absolute" (I think as I only saw it for a moment) and I think the label was something to do with paths. The screen flashed and the entire project disappeared from the Xcode UI even though it is open.
The folder created in my Documents folder by Xcode is still in tact and all files are present. Even opening the project from here renders the same result - a completely empty Xcode except for appdelegte.h and .m.
I have even tried restoring an earlier snapshot but it does not help. When I open my project all I see is the AppDelegate.m and .h and nothing else. The only item in my project navigator where I used to see all my files is my app name .xcodeproj in red text. I cannot find anything to help me get my project back.
Can anyone help me to reverse this simple mistake?
I was able to reproduce this problem consistently and cause Xcode to crash in the process.
1] Start Xcode (Quit and re-start) and create a new utility project named TestProj. I don't believe the project type or name makes a difference but I didn't try any other combinations. Do not create a GIT.
2] After the project is created, simply click on "Location" which is greyed out because the project is selected in the project navigator. Once you have done this, the project is hosed and you can't get the project to open in project navigator again - it simply shows "TestProj.xcodeproj" where the project used to be listed in the project navigator.
3] To see Xcode crash, selected "Relative to SDK" and Xcode dies.
I have accidentally clicked on that greyed out location twice simply due to my apparently terrible mouse skills.
Apple, please fix this!
After reading:
Accidentally changed location of project file in file inspector, now can't see any project files in Navigator.
I went to Xcode (4.3 on Lion in my case), selected the project on the Project Navigator (left Xcode panel) and in the File Inspector (right Xcode panel) I updated its location to the Relative to Group value and then clicked over the little image button (underneath the location line) and selected my project.xcodeproj from Finder. It also solved the problem.
Best regards.
Ok - problem solved.
Eventually Xcode opened without crashing and with a seemingly useless file listed on the left in the navigator. I highlighted it (which is when Xcode was crashing all the time) and immediately clicked the in the project name text box in the inspector and entered my project name. Then selected the drop-down beneath it and selected relative to SDK. As soon as I let go (mouse-up) it changed to "Not Applicable" and my project re-appeared. Happy days! Only lost a day worth of work - but could have been worse...
Thanks to everyone who gave this some time...
I just upgraded to Xcode 4, and I'm trying to open a project I created with the previous Xcode, but when I open it, after about 1 second, it hides all the folders and inline projects in the project navigator, and only shows the "resources" folder. Strange behavior. I can compile and run, but I can't edit my files from xcode any more.
Anyone else see this?
#haider I had the same issue with XCode 4.3, tried the above recipe, but it did not work for me. Here is the correct answer to prevent this from happening and get it to work right:
There's a tiny row of icons to the left of the search box under the left hand nav. The first of these is a '+' (to add a file). The icons following the add-a-file icon are actually filters that can be toggled on and off. The first of these looks like a clock, and is a filter to show only-recently-modified files, the second to show files-with-source-control status and so on. I must have accidentally picked the first icon after the '+' (show only recently-modified files) and therefore had the problem. The XCode UI preserves that pick even when you close the project so closing and re-opening does not alleviate the situation.
Don't know why it fixed, but it did. After closing down xcode and restarting several times, it ended up working ok again. Strange