Hi, I've just started using Visual Studio Code as my primary code editor and it was working fine for the past couple days, although today when I opened it and tried to edit a file I couldn't. Whenever I tried to write anything the file wouldn't get those words and the cursor would just jump between points every time I clicked a key. I was wondering what is causing this and how can I fix it?
And just an additional point, whenever I go and click on a word, rather than giving me a normal typing cursor I'm getting a cursor which you primarily see in terminal windows where it's a rectangular box
Your screenshot shows 45k+ problems. You have quite possibly deleted something important. Check if the following command works in the terminal.
flutter clean
Related
I occasionally bump into this issue where when I'm typing code on android studio after some time the code gets auto-highlighted on the current line to the current cursor position while typing, hiding what I'm typing in the process. this really gets annoying especially when i need to review a particular line (which will also get auto-highlighted on gaining focus).
I have tried to search for the cause of this and perhaps how to fix it but no related problem posted here I've been able to relate mine with. So far the only solution is to restart Android Studio. The rest of the editor functionalities work fine so far.
On Windows:
Close Android Studio first
Go to your User Folder - on Windows 7/8/10 this would be:
C:\Users\ (ex. C:\Users\username)
In this folder there should be a folder called .AndroidStudio (Note: it would be hidden).
Delete this folder (Backup it before to another location).
This should reset your Android Studio settings to default.
As the title states I am making an app with android studio. I recently installed git as well in order to interface with GitHub. For some reason whenever I change the layout on the layout editor, or type more than 3 characters of code the git terminal opens up multiple windows, then they disappear, and I get no errors of any kind. It repeats indefinitely and I am really unable to get any work done because of it. Has anyone seen anything like this before and if so I would love any help I could get. Thank you! I tried to make this as detailed as possible hopefully it isn't too broad.
I have a question transitioning from Eclipse whenever I start to type something for a string or even for a Log.d i would get "" to automatically appear, which I've found out how to do this in Android Studio no problem, but in eclipse I use to be able to hit [TAB] and it would instantly jump outside of the " on the end so I can continue to type quickly anyone know if this is possible in Android Studio?
Unfortunately, this is currently not supported in Android Studio. The closest command to the desired behaviour would be Complete Current Statement (Ctrl+Shift+Enter) which only really works if you have only one parameter.
I am new in using Eclipse and I am facing many problems. The first is that if I write an instruction wrong - for instance: android:layout_height="wrap_contet" and not content - the IDE does not visualize any error and this is very annoying.
If I change the dimensions in the values resources the picture does not update in the render preview. I need to close the program an restart it, just then the picture gets updated.
It is like the IDE is just ignoring half of the things that I write down. I click on F5 many times to refresh but nothing gets refreshed.
First I used Android Studio and I did not have these problems.
Try This go to Project->Clean, it will provide an Updated version of your project.
First if you are using Windows then go to Window->Android Virtual Device. After you start your AVD you will get your first issue solved regarding wrong instruction it will show error on the left after saving the xml file.i need more info on your second issue.
I am a little bit new to developing for Android using Eclipse (Coming from a .NET/Visual Studio background).
My biggest problem in developing Android app is "debugging" them. Every time the emulator throws an error, there is no message, no explanation of what caused the error. I basically have to keep doing trial/error until something works.
My question is: Is there a better way to analyze the error messages that emulator shows (basically some stack trace about Dalvik)!
Also, is it possible in Eclipse [when debugging] to move the debugging cursor backwards to re-evaluate a variable or "skip" some lines of code?
Use LogCat view to see error/debugging messages. Regular console is of very limited help. Window->Show View->Other->Android->LogCat There on the top you will see some round buttons that basically can filter log from V (verbose) to E (error). You can't copy/paste from theLogCat window but you can save selected output to text file
Regarding the error messages (I'm assuming these are the messages that show up in LogCat): I've found that analysing the error messages and working your way up the list until you reach code that is yours is the most effective way to work. Frequently (for me at least) the emulator will crash and break somewhere in the OS code (which you probably don't have the source for) but you can follow the LogCat messages back to your code and start to see where the problem is. The crash may appear to happen in the OS code, but the original cause is typically you passing something wrong to the OS.
Regarding going backwards in code: nope, at least not with the my Eclipse Ganymede install
Regarding skipping code: When your in debug mode under the Run menu you can select "Step Over" (skips going into a method) , "Step Return" to exit a method and "Run to Line" in addition to setting Breakpoints by right clicking. This causes the code to run, but you aren't single stepping through it. Otherwise the only way to "skip" lines of code is to comment it out. I believe you can also change the value of variables in the debugger, but I've never tried personally. This may give you the desired effect.
Try closing all unrelated project, switch off eclipse and then do a clean and build for the project in picture.