I have been having a running problem with the location simulator for the last couple of weeks.
When I enter updates of Latitude and Longitude, I note that they do not have any effect on the actual location. Similarly, when I try to drag the map to a new location, I don't see any response either. The hand cursor is no longer shown when the mouse cursor is over the map. An I-Beam cursor appears, instead.
Also, the zoom buttons are no longer shown so it's not clear how to zoom in and out on the map.
I had filed this issue in a different Stack Overflow question. I got some responses, which turned out to not be sufficient to solve the problem.
Unfortunately, I then had to deal with an unrelated issue and was away for a couple of weeks. When I returned, I downloaded the latest build and tried the simulator.
I noticed that several changes were in place in the location simulator, including being able to enter a new latitude, longitude, velocity, etc. Also, the Update button was no longer present. However, the same issue was present where none of the changes had any effect on the actual location shown in the simulator.
Not sure if I'm doing something wrong or if there is still a bug in CN1.
Since I don't hear a lot of other people grousing about this issue, I'm guessing it's some configuration or installation problem on my system. However, I have not had any response to my comments or questions on Stack Overflow.
I wonder if there is a particular version of Java now needed to run CN1 on eclipse Mars? I updated Java to version SDK 1.8.0_77, which appears to be the most current version according to java.com. I restarted eclipse and found that it and CN1 seem to run okay. In the location simulator, I see no change to the behavior at issue. Location UI still does not accept user input
Since I have a Professional CN1 license, this is the only help/support available. I can't afford the Enterprise license. The turnaround time on any questions/responses appears to be about a day, due to the time difference (Tel Aviv vs Minneapolis).
I added a reply several days ago now on my previous thread on this issue and never got a reply. So I am starting a new thread. Hopefully that will get some attention.
This issue is becoming a real roadblock to my getting work completed. I note you talk about how your updates are making CN1 easier to use. So far this has nothing but frustration - end of vent... :-)
Essential Stats:
IDE: Eclipse Version: Mars.2 Release (4.5.2)
Desktop OS: Windows 8.1
Using Simulator
Thank you,
-Craig Lang,
Horizon Technologies
I wasn't able to reproduce the exception you got but I think we do need to put out a warning when running under JDK 7. We'll look into that.
Related
My visual studio code seems fine and all of the sudden boom its crashed. Searched google for the error code No solution found. Any help would be appreciated.
error code = -536870904
Whenever anything stops working for no apparent reason then think:
Did it work before?
No, it is new or it has not worked yet.
Check your download, ensure it is compatible with your operating system and other running programs.
Yes, it used to work, but now it doesn't.
Look at the next step
Did you recently update the program, your operating system or any other programs?
Yes, I updated something.
Try rolling back your updates to see if it works again. New versions of software tend to be more error prone than the older, established versions.
No, I don't think I changed anything.
Either you are unaware of changes made to your system or some subscription has ran out. At this phase, the best option is to use common sense or uninstall and reinstall.
Another issue that you might be having is if you're running too many programs at once and your computer is force closing programs to protect itself. Try monitoring your Task Manager you may see a spike right before the crash. Also, make sure the crash isn't caused because of trying to run code (especially with code that has infinite loops)
The problem
Hi, I have been experiencing this kind of loading infitely on the window screen: "Application.Reload" since two or three days ago. This just happened spontaneously without any reason. I have been seaching for a solution, but the uniques fixes i had found are not working for me.
The unique not permanet solution that I came up is just use the Task Manager and close up Unity.
The possible fixes that I have tried:
"Just locate the project folder in the system explorer and click on properties" (This only work one time per application or maybe it just do not work.)
"You can check to see if there is any place in your project path that is not in English" (It just do not work.)
These are the fixes that I have tried.
Example of the problem
Meanwhile I am writing this question, I want to re-confirm this is a infinite load. So I open up my Unity Proyect, enter in the Play Mode and write this question.
This is the result:
https://i.stack.imgur.com/sTA48.png
Edit: the image actually shows the longest time i have been waiting. (1:48:34hs)
Thank in advance for any kind of help!
As I know, this problem persist as well in any Unity Operation, it can happen on Reload, Importing, Asset Indexer, etc. Is just a problem that doesn't affect Unity, and devs marked it as WNF (We'll Not Fix).
I have been struggling with this problem for some years now and the only solution I found was to close it from Task Manager and reopen it.
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..
Bounty Update
I am leaving the question essentially the same, but I just want to point out at the beginning here that I'm most interested in help trying to get the socket between flash (Adobe Animate) and the native debugger working again, as I believe that is the issue I'm having. Or is it a socket between flash and Windows?
Original Question
I've apparently turned something off? Even when I write really bad code (like trying to call a function that isn't there or divide an integer into a fraction), the flash player boots, shows a background color and stops there. No messages in the output window or compiler errors window. If I fix my code, it all runs fine, but for about 30 minutes (ever since I started trying to work with bitmaps for a sprite sheet) I get no runtime errors no matter what kind of mistake I type in my code. Anyone know how to turn it back on?
I've checked my actionscript settings and I have both warning mode and strict mode checked on.
Could it be a socket issue? I admit I have little to no experience working with sockets and only a surface understanding of what that even means. I've added the socket tag. If someone can see that this is clearly nothing to do with sockets, by all means, I'll remove the tag.
UPDATE: 6/22/16
I just reinstalled Adobe Animate CC 2015.2 and no change. I'll try compiling it in flash builder when I get a chance to help pigeon hole the problem. (Edit 6/24: flash builder worked! But my trial version expired the next day so is no longer a viable option).
And I just tried something in the command prompt in Windows 10 as an administrator:
netsh winsock reset catalog
netsh int ip reset reset.log hit
which I found another user on flashdevelop.org used to fix a similar issue, but no change.
And I just tried debugging in Flash Builder. It worked fine (debugger caught bugs) but my trial version expired the next day.
update 6/24
I've tried launching debugger for AIR from within the Adobe Animate CC IDE and it works fine if there are no bugs; it fails to do anything visible (no Iphone emulator, no swf window) if I put a typo or error in the code.
I also just deleted winsock and winsock2, rebooted Windows, then reinstalled winsock and winsock2. No change.
update 6/25
Just tried a system restore in Windows to set all my files and settings and drivers etc. to the way it was a week and a half ago... Also completely uninstalled all Adobe products and reinstalled. No change. I can only imagine that wiping my hard drive and reinstalling Windows would do the trick, but come on, it hasn't come to that has it?
As VC.One suggested, I checked the compile error window (cannot believe I didn't check before! Maybe when I checked before there were no compile errors... Only runtime errors?) and the errors are showing up there. Does this mean that it's catching compile errors but just not runtime errors?
When you force/test a runtime error... make sure you check
Compiler Errors (ALT+F2) and also Output (F2). By Output I mean the window that shows traces (and runtime issues). One of those two should have some feedback for you.
A possible solution is to save a new Workspace. So with those windows for Compiler Errors and Output both open (or tabbed, I tab them next to my Timeline) go to Window (in top options like File/Edit/Debug etc) and choose Workspace, then into that you choose New Workspace. Give it a name in the pop-up and okay everything.
Flash should always load that current workspace (next time, go to Workspace option again, check that your specified workspace [by name] has a tick next to it...).
Possible pitfalls:
1 - Use the debug player
2 - Make sure there isn't somewhere a try/catch enclosing the portion of code that triggers the event that may lead to an error
3 - Socket issue: may be exported in debug mode but swf cannot connect to debugger (it waits in a blank state for 60 seconds I guess)
4 - Does it compile ok? If there are compilation errors you may get an SWF anyway but then it will not start
...
(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).