With MonoDevelop 2.8.6.4 I am getting asked many many times a day if I would like to load a file from AutoSave even though there was no crash and the files were closed properly. The only way around it for a little while is to delete the MonoDevelop 2.8 cache folder over an over again.
Is there a work around for this bug as it's very time consuming to work with.
I believe this was fixed a while back and the fix will be in an upcoming MonoDevelop release. It's triggered by having the "format on save" preference enabled.
Related
I'm using Android Studio 1.5.1 on Kubuntu 15.10 and lately, Android Studio freezes completely whenever I right click into the project explorer. The only thing I can do then is to kill the process.
More oddly, whenever I hover the Help menu with the mouse, the complete OS freezes completely and I have to restart the computer. I am not 100% sure if these two issues are related, but they started at the same time.
Sometimes (about 10% of the time) it works well. I have no idea what influences this pattern, though. This used to happen earlier as well, but much less frequent.
The usage of different color schemes or deactivating plugins seem to have no influence on this behavior. I also did not install any fishy third party software or anything else that could (to my knowledge) have influenced this. Any ideas?
The issue seems to be resolved in the latest stable release (2.0).
I've recently run into this as well. Pointing jstack at the hung process suggests that it's this problem.
Switching to the Darcula or GTK+ theme resolved it for me. Weirdly, I can switch back to the Intellij theme afterwards and the problem stays fixed - I just have to switch to GTK+ or Darcula at some point after startup but before triggering a right-click menu.
Edit, 1 day later: In a deeply unimpressive plot twist, this solution no longer works for me. I've changed nothing since yesterday, but now attempting to switch themes triggers the lockup ಠ_ಠ
Edit, 1 day, 5 minutes later: After a restart the situation improved slightly - changing the theme now works again, and avoids the freeze-on-rightclick failure. I'm finding it difficult to take this as much of a victory.
Edit: As karpfen notes below, this issue has been resolved in the latest release. Huzzah!
The current Android Studio version has inbuilt auto save. Which means if you close a file, it will automatically save the changes.
This is inconvenient, it means when experimenting with code, all changes need to be noted as there's no option to have a dialog requesting to save changes on closing a tab or the project, as in many other ides.
According to documentation IntelliJ IDEA 15.0 Help/Saving and Reverting Changes:
When does IntelliJ IDEA auto save changed files?
Autosave is initiated by:
Compiling a project, a module or a class
Starting a run/debug configuration
Performing a version control operation such as pull, commit, push, etc.
Closing a file in the editor
Closing a project
Quitting the IDE
.../...
Note that those are optional autosave triggers, and you cannot turn off autosave completely.
These are the auto save settings that can be changed in Android Studio:
TLDR
Is there any work around to circumvent this autosave?
These questions are related, but do not acknowledge that this intended behaviour of the ide and are rather asking for fixes within the ide.
Related:
How to disable Auto Save save in Android Studio
How turn off autosave in Android Studio?
If you want to experiment, use the revert button at the top right. This works especially well if you are using a VCS (like git...) as it will revert to the last committed version. And since commits are still manual, this will soon replace your traditional save.
If you are not using a VCS the point in time to which it reverts is a little more arbitrary, but in my experience it takes a pretty good guess. If that doesn't suffice, you can use the history button next to the revert button, which keeps track of every version IntelliJ saved, and you can then go back to any point in time you like. :)
Android Studio as a software is very much based on the JetBrains software solutions such as IntelliJ (used for Java) and PHPStorm (used for PHP, as its name shows).
As a concept in itself, JetBrains have implemented this feature and as a company believe that it's much more efficient and productive than manual save. Hence, there is no way to disable this behavior or enable any confirmations in Android Studio either.
Taken from JetBrains FAQ for IntelliJ:
Because IntelliJ IDEA has the ability to change so many files simultaneously in large refactoring actions, and change them without ever opening them, single file saves don't make very much sense. In recognition of this, IntelliJ IDEA reserves the right to save any of your files literally whenever it wishes. It's actually quite nice to never have to worry about your file's save statuses, once you get used to it.
Having said that, and encountering this issue myself too as a developer, I agree that it would be a good idea if the Manual Save feature were enabled by the Android Engineers (or JetBrains themselves). After all it is up to the developer to choose whether he needs this feature or not.
To Jetbrain's defence, they have a very good Undo function through their Ctrl + Z shortcut keys, letting the developer go back many steps and find where a certain error has occured.
All IntelliJ based products nowadays save any opened or modified files whenever they wish - read this as "immediately".
I would suggest you give up on trying to disable it (trust me, it's not possible to hack it) and either change your work flow or work on copies of the files.
As background I should mention that I am a plugins author for IntelliJ (with 3 publicly released plugins in the JetBrains repository) and thus have a reasonable understanding of the internal IntelliJ architecture.
This question already has answers here:
Microsoft Excel ActiveX Controls Disabled?
(11 answers)
Closed 8 years ago.
Today, out of the blue, a form that the company I work for uses, suddenly had an issue with it's buttons. Strangely enough it only is affecting what I'm pretty sure are the ActiveX Command Buttons and not causing a problem with the other shapes or drop downs.
The issue. The buttons are non-responsive. When you click, they don't access the code and checking them via the shapes menu and selecting "view code" causes them to open the developer menu, but not the code associated with them. The really big issue is that for some reason they ALL seem to have started failing at the same time. The version on the server no longer works (the primary copy), the copy the user uses (notorious for breaking things) and the version I use (which is on my local computer).
Is there a way to take them an re-associate them with the proper code, without deleting them completely re-making them or is there possibly someone who's had the same issue and figured out a fix?
I'd greatly appreciate any suggestions or help - please note: I'm 99.9% sure that the issue is not code based.
The problem is caused by a recent Office update. Here is the fix posted on http://excelmatters.com/2014/12/10/office-update-breaks-activex-controls/
To fix it, do this:
Close all Office applications.
Do a search in Windows Explorer – make
sure to include hidden and system files and folders – for *.exd files
(note: that’s not *.exe !!) and delete any you find.
Make sure you get these:
C:\users\username\AppData\Local\Temp\Excel8.0\MSForms.exd
C:\users\username\AppData\Local\Temp\VBE\MSForms.exd
Reboot the computer (this is not always necessary, but probably better safe than
sorry)
Restart your Office apps and test the controls again.
When MonoDevelop crashes (somewhat often unfortunately) I usually have to re-do changes to the project that seem to not be written to disk. As a result my work flow has become - change project, restart monodevelop (hoping changes are saved during a close). I find this to be a little frustrating. Ideally there would be an explicit save button in the UI so that I know for a fact my changes are written when I expected them to be. I am not sure where to file enhancements requests - through Xamarin (since this is monodevelop with monotouch)? Any chance someone has written an Add-In to do this?
If everything is OK with your MD installation the Save All command/button should save all the project files and solution. I regularly use this command as a safeguard. On my experience just hitting Save only saves the file you are editing on the moment, keeping the solution and project files unsaved.
Today I tried to made "Code Cleanup" of single file in ReSharper 6.0 (VS 2010). The Code Cleanup dialog did not show up so I tried again.
I then discovered, that the feature is grayed out and when I press hotkey for Code Cleanup, the notification area shows that the "command is not available at the moment".
Even the Code Cleanup settings are hidden. The panel where settings should be shown says that the settings are solution-specific and thus a solution needs to be opened (although it is, however).
All other solution-specific settings and features work, except for Code Cleanup.
I want to avoid re-installing ReSharper or resetting its settings, because otherwise I would need to set it up again (long and annoying work of setting all the options as before re-install).
I am afraid that backing up settings and restoring it again restores the problem as well.
Any suggestions?
Suggestions:
Ensure that the file that you're trying to cleanup is included in your solution.
Try to reopen solution (close and then open again).
Upgrade to 6.1.1, maybe its fixed there.
File a bug report at http://youtrack.jetbrains.com
Both ReSharper 7 and 8 seems to work OK.
I know this is an old answer, but I found a little more insight on this. According to Jerrie Pelser in this blog post from last year, this may have to do with the file being part of a NuGet package. In my case, this was definitely it!
In case of link rot, basically the post mentions that ReSharper will avoid refactoring/code cleaning for files it detects were added as part of NuGet packages. This is similar to how it will not allow code cleanup for generated code.