The editor window does not fully render and is unresponsive... I restored windows by completely reinstalling it, fresh install, all clean... and still same issue:
I checked Unity 2017.3, 2017.2 and 5.6, with DX9, 11 and 12... allways same issue.
I found 0 related issues on google, maybe I'm not using the correct wording for the search (Unresponsive Unity Editor Windows). On the Unity forums someone mentioned DX version being the issue, but I already forced all recent versions and it fails for all of them.
Ok, so the issue is with Unity not being dpi aware so I had to remove my 150% scaling on my main 4K window in order for it to work.
Unity programmers my encounter this issue too, and come here for help as I did... I don't see why that's wrong #Programmer
Related
Overnight, any help I had for Unity3D in VSCode, i.e. intellisense, disappeared. And I get the sense, no pun intended, that I'm not the only one who's afflicted.
I've tried updating and reinstalling what I assumed VSCode needed to make Unity3D intellisense work. And have checked and re-checked settings, reinstalled VSCode package, in Unity3D.
I've worked through a few tutorials that claimed to address the issue.
What else does VSCode depend on to make this relationship work?
Thanks! Here's to hoping you've fixed this and your life has gotten easier!
Try going to Edit > Preferences > External Tools > Regenerate Project Files (This is because of a bug where the VS Code extension doesn't generate the project files correctly the first time, you can check it out here).
You'll need to be using the VS Code Editor Extension 1.2.0 (you can check which version you're using in the package manager) or later for that option to appear. Also if for whatever reason there are 2 .sln files in your project folder (I've had that happen before, though it's less likely), that also causes problems.
Ok. First, thanks to Lightning_A and Charleh!
The resolution to my specific circumstance was to install the VSCode extension "Unity Snippets Modified" https://github.com/with-heart/vscode-unity-snippets
I had been using https://github.com/kleber-swf/vscode-unity-code-snippets.
Perhaps it's just a matter of Kleber's extension, which is/was great, was broken upon updating Unity to 2020? I dunno and don't have the time to look into it, unfortunately.
Hopefully, my question, the answers I received, and my subsequent resolution saves others from the rabbit-hole I went down.
Again, thanks everyone!
I have a monogame project created in visual studio with MonoGame 3.5. After running it on linux, mouseState.ScrollWheelValue is always 0, regardless of anything I do.
This most likely has to do something with the fact that linux has different window focus regarding mouse wheel, but I can't seem to figure it out.
What I found so far:
1. I should set Mouse.WindowHandle to correct value (whatever that means).
This is largely problematic, since Mouse.WindowHandle setter is not implemented. Plus injecting a specific window into the Mouse object is an internal procedure. (source: https://stackoverflow.com/a/33921015/3455388 )
2. A poor soul that asked this question on official monogame forums 3 years ago, with no visible answer (https://community.monogame.net/t/mouse-state-scrollwheelvalue-returns-0-all-the-time/9233)
Does anyone know how to make MonoGame receive MouseWheel events on linux? An answer that this is simply not supported is also fine.
I have no idea why, but resolving a different problem related to sound resolved the mouse issue as well.
When initially running my game on linux, I got a second issue with sound library: Unhandled Exception: System.DllNotFoundException: openal32.dll. I simply disabled sounds and dug in the MouseWheel issue.
After giving up on the mouse issue, I returned back to fix the sounds, and found a guy talking about missing files in the /bin/Windows/Debug/ folder (https://github.com/MonoGame/MonoGame/issues/657).
Turns out my MonoGame bin directory only contained OpenTK.dll, but was missing OpenTK.dll.config. Copying it from /usr/lib/mono/xbuild/MonoGame/v3.0/Tools/ resolved the sounds... and the mouse. I guess the missing library might have crashed the initialization process before the mouse was correctly set up..
I'm having a problem with the built-in help/documentation within MATLAB 2013a (issue also present in 2012b).
Upon opening the help files the pages appear with no formatting, only plain text. Search results do appear correctly though.
I have found only one instance of someone else with this issue, on MATLAB central here. However, there are no responses to the author's question. The issue I'm having is exactly the same as described there.
I have tried removing the preference folder and relaunching MATLAB but this doesn't help.
I'm using Windows 8.1 and MATLAB 2013a.
Any help or suggestions on how to fix this would be very much appreciated.
Edit:
Thank you everyone for the feedback so far. I don't believe java to be the issue, I have the latest version installed (1.7.0_45) while MATLAB uses it's own version (1.6.0_17). Both of which co-exist on my machine.
Following horchler's thread led me to another semi-related bug report here. The following code is listed at the bottom of the workaround (the script attached to the workaround didn't fix anything unfortunately).
com.mathworks.mlwidgets.html.HtmlComponentFactory.setDefaultType('HTMLRENDERER');
This results in a degraded appearance of documentation pages and loss of some functionality but is still an improvement over the plain text and scrambled pages.
Hopefully from this new information we can work towards a solution!
One solution is to go back to IE-10, or to use the patch on http://www.mathworks.com/support/bugreports/989850
Which basically replaces the localnav.js at <MATLAB>/help/includes/product/scripts
The link to download!
This is an old post, but I had the same issue and have a fix (not downloading R2013b or java related). Just downgrade from IE 11 to 10: Go to System (or System & Security)->Windows Update->View Update History->Installed Updates -> Find IE11 and uninstall it. Your system should revert back to the prior installed version. This fixed the help issues.
The problem is related to Internet Explorer 11, which MATLAB uses to render its help files. I was experiencing this problem in Windows 7 and rolling back to IE 10 fixed it right up. Unfortunately, that's not an option with Windows 8.
(Running MATLAB 8.1.0.604 (R2013a), Mac OS 10.8.3)
When I use the doc command, for example, doc fwrite;, or when I click the "more help" item in the popup help bubble for a command, the documentation window opens, but MATLAB subsequently hangs (the spinning beachball appears). This lasts indefinitely, and I inevitably have to force quit MATLAB. This also happens when using the Publish option from the editor.
Anyone have any ideas for diagnosing this? I tried taking a process sample but I didn't see any info I could interpret, I think since it's in Java the relevant information is obfuscated behind the JVM.
See this post on MatlabCentral: http://www.mathworks.com/matlabcentral/answers/71718 ... and more specifically this bug report which includes a "workaround." They don't suggest what could be the cause, but you might make sure that OS X is updated and that you have the latest version of Java. If you do other work with Java or with WebKit these might cause issues.
I hope you have already solved the problem. Otherwise a solution has been found, the bug resides in the Access for Assistive devices (only for version 2012b and later). If you can turn them all off from System Preferences, do that. If you can't, type this in the command window:
com.mathworks.mlwidgets.html.HtmlComponentFactory.setBrowserProperty('JxBrowser.BrowserType','Mozilla15');
From http://www.mathworks.com/support/bugreports/870843
I had the same problem with Matlab R2014a on OS 10.10.4. For me the solution involved disabling Cinch (a window management tool I had installed). This can be done by clicking on the Cinch icon in the menu bar then Disable Cinch, or from System Preferences > Security and Privacy > Accessibility (as MarcoB detailed in his answer).
More suitable as comments (but I don't have enough rep yet):
I just updated to Java 1.8.0_73 and to Safari 9.1 and the patch horchler posted no longer works.
MarcoB's command still works for fixing the crashes. But with this, no longer retina resolution in the Doc browser (so it looks ugly).
I recently upgraded to NetBeans 7.2 and am facing a substantial usability issue with floating windows. In 7.1 each floating window was minimize-able, which I used quite regularly. By all appearances the minimize button is completely gone. The button is missing and when I right click on the title bar, the close button is available but the minimize is disabled (greyed out).
I'm running windows 7 x64.
I also encountered the issue in the RC but figured that it would be resolve in the final version. I've googled around and not been able to find anyone with the same issue so I'm hoping that it is just me.
I checked out the settings under Tools > Options > Miscellaneous > Windows and none of them seem to make any difference.
How can I get the minimize floating windows functionality back?
It looks like a bug on the windows version, because I'm using the mac one and the minimize buttons are in place.
I'd go back to the previous version until they solve the bug.
In fact, at least in mac, you can have both versions installed, so you could open 7.2 from time to time and check for any updates that solved the problem.
I've found some additional info here:
https://netbeans.org/bugzilla/show_bug.cgi?id=216019
Maybe you could try to do as they tell:
No minimize button means those windows are docked into editor docking spot. Use
menu Window - Reset Windows.
I am able to minimize windows in netbeans on win 7x64
And sorry I wanted to add this as a comment, but apparently I couldn't