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 :-|
Related
I have only been able to find 1 add-on for autosaving/draft-save.
The problem is that if the browser crashes while you are editing content of a page, or created a new page, that changes will be lost. And it's not always, that one will remember to save manually.
The add-on I found and installed is: plone.app.drafts
I installed it using buildout, and activated it in the add-on. Though it doesn't seem to be working for me. Has anyone managed to make it work? To test it I crashed the browser (and also just closed the browser while editing), and according to the documentation for this add-on, the saved content should be in portal_drafts. But there is nothing there.
I followed this document.
Stackoverflow has the best auto save future EVER. It would be nice with such, but just a normal auto save will do fine.
Are there other plone fans out there that have managed to overcome this hurdle? Like found a nice add-on to help out?
do you want to auto-save input in richtextfields (tinymce) or all fields?
for tinymce there is a plugin you could try to add:
https://pypi.python.org/pypi/zopyx.tinymceplugins.tinyautosave/1.0.1
When:
Live Preview is running
I'm writing CSS
& I hit Enter to use an auto-completion recommendation
Then:
The auto-completion occurs
The cursor skips down a line & indents
I usually work around this annoying cursor movement by closing Live Preview, but I'd really rather not. Is this a bug or am I missing something? How can I fix it to where it just simply fills in the auto-completion recommendation?
Thanks!
Brackets 0.41
Windows 7
Brackets doesn't normally behave this way - you may have an extension installed that's causing trouble. Try using Debug > Reload Without Extensions and see if the problem still happens. If that fixes it, you can systematically disable individual extensions until you find which one was causing the problem. I believe the "Emmet" extension has caused some similar issues in the past, so that might be a good one to check first.
Once you know which extension causes the problem, I can walk you though filing a bug with the extension's author so it can be fixed.
If you're seeing the issue even after Debug > Reload Without Extensions, then it would be good to get more specific with the steps that trigger the problem. For example:
Open the default "Getting Started" project and open its main.css file
Start Live Preview
Add a new line to the end of the body rule
Type font-w and press Enter
type b and press Enter
When I do these steps, no extra newline is inserted. What steps should I use instead to see the problem?
I found this as I was experiencing the exact same issue. Try disabling any scripts called in your html one by one to see if it goes away. My issue was a script I was loading from a Wu
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 just started a MVC3 Razor application and started typing out in one of the .cshtml files and I added an a tag with href, when I entered the location it keeps telling me to use a directory that it wants me to use. I cannot get rid of this and it is always visible.
Does anyone know what this feature is called and how to disable it either permanently or for certain files, either way is good. I tried looking through the options but with no luck.
Image:
Go to ReSharper > Options > Code Inspection > Inspection Severity
Search for "path error" inspection
Set inspection severity to "Do not show"
This is a new feature for Resharper 6. I recently uninstalled it (rolled back to old) as it was causing 'out-of-memory' exceptions for me.
So, it may not be 100% on the spot but I think the feature you're looking for should be under Coding Assistance | Code Completion.
If you cannot customize that specific option (which I think you can't) then the other option is turn off the whole Code Analysis thing.
IF this doesn't solve your problem, I'll try to find you an exact answer later.
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.