I.T. gave me an upgrade to V5 and I can't see my directory listing.
Maybe I bumped a hotkey i don;t know about?
You can see a screengrab here http://dl.dropbox.com/u/23768853/help.jpg
I'm combing thru all the preferences but so far nothing, anyone know how to make it come back?
Fixed !
I.T. re-copied the application into the application folder and webstorm is working normally again.
Surprising to think that the application can run even after a corrupt install.
Related
I am using the newest (updated) version of IntelliJ IDEA. I am coding in Javascript (React) and i've been using the One Dark theme for ages now.
But since the last update, everything is glitched.
So first problem:
The IDE is now allways starting in the white theme (which is related to the windows theme)
When i try to change the Theme, either nothing happens, or it just doesnt show any Themes, even tho i installed more than 14 (they are disabled tho).
Second problem:
I can not code in Javascript anymore. There is just no collor at all. No marking for functiond etc.
Third problem:
My IDE is crashing almost everytime, I try to open a new, or existing project.
Why is that, has someone simular issues, and what can i do, to prevent having to reinstall my IDE, as i do not want to set my IDE up again.
Thank you in regards
You will have to reinstall. But you can save the Config file.
So you can keep all your settings.
Here are the Paths for windows
Windows:
Configuration: %APPDATA%\JetBrains\IntelliJIdea2020.3
Plugins: %APPDATA%\JetBrains\IntelliJIdea2020.3\plugins
System: %LOCALAPPDATA%\JetBrains\IntelliJIdea2020.3
Logs: %LOCALAPPDATA%\JetBrains\IntelliJIdea2020.3\log
Hope this helped.
The find in path search works on newly cloned/downloaded repos. But I notice after a few days, all search functionality in the IDE just stops working. Searching for anything string turns up 0 results in project, module, directory paths. Anyone else experience this? It's infinitely infuriating T.T
OS: Mac
Version: Intellij IDEA Ultimate 2020
Settings: only default
Please, try to invalidate caches via File | Invalidate Caches / Restart option.
It's a known issue IDEA-266391 and you can update IntelliJ IDEA to the 2021.1.1 version with the fix.
So it turns out this is happening whenever I change branches. So your suggested soln above works well. thanks!
Below you can see the output I get when I try to run npx react-native run-android. It suggests some options to try in order to further pinpoint the problem, however they don't work with the aforementioned command so I assume that they are related to a gradle (just an educated guess).
I know ZERO about gradle; I have just seen the name here and there and in the output shown below. So please keep that in mind when you answer. If I need to learn how to run some gradle command(s) directly, please be as verbose as possible in your answer.
The project was working fine just a bit ago, but I wanted the ability to force portrait mode for certain screens but without configuring my entire app to always have to stick to portrait mode. So I found what looked to be a solution in the react-native-orientation-locker module. I installed it with yarn and then proceeded to update files as directed: https://www.npmjs.com/package/react-native-orientation-locker.
After updating the appropriate files, I got an error that suggested axios was the problem. I uninstalled and reinstalled axios. After that didn't work, I proceeded to undo all the file changes I had just made. Then I uninstalled the react-native-orientation-locker module.
To my knowledge, I have undone everything I did between the time the project worked and stopped working.
Sadly, I had not put this into source control yet (a mistake I won't make again), so I can't revert.
Where to go from here?
Problems like this are hard to pin point. What you can do is open the android project in android studio and see the logs as the project is being assembled. I assume you do not have much knowledge about android either so you might need some senior resource to help you.
What I usually do in this case is open android studio and if I am lucky enough, it tells me which file has an issue and I go to the file and do what android studio suggests me. Some times it fixes the problem and sometimes it doesn't.
Another thing I would like to mention is that the documentation of the package you are using is important to follow. I assume you did that already but I would suggest to review it narrowly and closely.
Another guess I can tell you is try to go to your-project/android/build.gradle and over there, you'll see something like this in the start. The package you are using mentions something about target SDK 27. I think you should check that out too. May be it helps
Lastly I would say always use source control while working with react native. It can easily blow up at any time so you should always have a safety net to fallback to :)
While developing a Cocoa sandboxed application, I discovered that if I switched it to non sandboxed, in all the Open Panels of the application, the right click commands (Duplicate, move to trash etc.) do not work any more. I am certain they did work no more than two weeks ago, but I have reverted the project to old commits and the misbehaviour is still there. I tried everything, until I realised that this misbehaviour now appears in all my projects, if I switch them to non-sandboxed. This makes me think it may be some kind of bug introduced in 10.14.2 or something similar. I hope somebody else has experienced the same issue so that we can understand better what is going on. Thanks
P.S. I am using the latest Xcode 10.1 (10B61) and tried on several machines. It is the same misbehaviour.
The OS might be confused by having some contradicting leftover knowledge about sandboxed and non-sandboxed versions of the app with the same version / bundle ID / signature.
Some things to try:
Test the app on a fresh user account.
Delete the app sandbox container from your Home Folder > Library > Containers.
Temporarily change app bundle ID to something new to see if it’s still affected.
I love Aptana, but sadly it crashes on me almost every day. I'm stubbornly sticking with the editor, but if I can find and fix the instability, I will have no major complaints with it.
I'm running Aptana Studio 3, build: 3.0.9.201202141038 but the crashing has been ongoing ever since I installed Aptana 3 many months and many version upgrades ago. Following the most recent crash I checked the Aptana .log but there was nothing valuable in there. There was however quite a bit of info in the OS-X "view details" notification following the crash: http://pastebin.com/02JrqrUQ
Sometimes it crashes following SVN actions, but also, as most recently, it will crash when it's just sitting there.
I'd appreciate any suggestions on how I can address this issue. I believe that I previously
had tried a reinstall which didn't fix the issue, but if no one has anything else to try, I guess I may give that a try again.
Thanks,
Dan
---- UPDATE ---
Ingo, Thanks for the response. That thread on appcelerator.org definitely describes the errors I was seeing.
Following your advice, I upgraded to the Aptana nightlies (now on version 3.1.0) and have not seen a crash in 2 full days. Hopefully any future crashes will now be few and far between and no longer a daily occurence.
Thanks so much for the response.
Thank you very much for your information. We've been tracking this issue, but honestly, it's been a bear to diagnose and reproduce, since most of the references don't point to any code of Studio--only the underlying versions:
https://jira.appcelerator.org/browse/APSTUD-3682
Please follow along on the linked ticket for more information. You might try the latest nightly (3.1 version) at preview.appcelerator.com which is built on top of Eclipse 3.7.
I had this same issue - and then I could not even open Aptana. Right click on the program -> click Properties -> Compatibility (Windows 7) > and tick "Run this program as an administrator"
This worked for me temporarily - the real fix is to delete or rename the .log file in your workspace.