My GUI was running perfectly well before I tried to change one little thing (it was only to print something to the screen, it shouldn't have made a difference). Suddenly I started getting this message
Undefined function 'Stacks' for input arguments of type 'struct'.
Error in
#(hObject,eventdata)Stacks('Stack1_Callback',hObject,eventdata,guidata(hObject))
Error while evaluating uicontrol Callback
Now even when I use my Time Machine to try to get back to old version of the GUI that I know for a fact worked they will not either.
Has anyone had anything similar happen or does anyone have any advice? I already tried restarting MATLAB.
Related
I've recently started receiving the following error whenever I enter play mode in the Unity editor.
Resolve of invalid GC handle. The handle is from a previous domain.
The resolve operation is skipped. UnityEngine.GUIUtility:ProcessEvent
(int,intptr,bool&)
This occurs every time I enter play mode, I'm not sure what I changed to cause this. The game still builds successfully without errors and I can't seem to find any issue with the game once built. It's worth mentioning that I may have noticed a slight dip in fps since I started getting the error. This is only while in play mode, not in the built player, although I might be imagining it, not sure.
I'm using version 2021.3.10f1, and recently updated from an earlier version, although have been using this version for around 2 weeks without issue.
Can anyone help?
I've been trying to set up the Scala layer and the Metals backend for spacemacs. I am relatively new to spacemacs and completely new to Scala. Quickly some problems, for which I have no idea how they can be connected to the Scala layer, arised. Firstly I got an error saying "package eldoc not initialized in layer java" despite the fact that I had no java layer installed at the time. I managed to resolve that one by installing the java layer and then deleting a line saying "eldoc" in the file at layers/+lang/java/packages.el.
Afterwards another problem appeared, which I still haven't managed to solve, namely now I get the following message upon opening spacemacs:
(Spacemacs) Error in dotspacemacs/user-config: Symbol’s value as variable is void: lsp-server-install-dir
I googled right about everything about this error and found absolutely no other reports of such a problem and nothing close to a solution.
I tried experimenting with disabling certain layers in .spacemacs and commenting out the lines I added before the problem appeared, but nothing changes or even more errors and warnings appear.
I am not sure if this is in any way connected, but after trying to install the Haskell IDE Engine into spacemacs a few months back, I got a warning, which still appears whenever I start spacemacs, saying:
wrong-type-argument stringp nil
This second problem seems to be harmless, so after a few days I gave up on trying to solve it and have been using spacemacs normally until now. This new error about lsp-server-install-dir, however, seems to be more urgent and spacemacs shows a red line at the bottom saying that it might not work correctly.
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
...
I am new to matlab and I've installed it successfully. Everything works fine. But when ever I try to open .m files, I always get following error popping out of dialog box:
Error using open(line 162)
Failed to open matlab editor.
And in command window it throws a lot of Java exceptions.
First of all please forgive my poor English.
I've been searching for this problem all over the internet but couldn't find any useful solution.
I'm using windows 8.1 pro 64-bit os.
Your error message indicates that there is an error in a line that justs consists of
<br>
This is not valid matlab code (looks more like html). As such it seems like you have either messed up the open function, or overloaded it somehow.
I think the first thing to do is check which open and see where this points you.
If this does not help, try to look at the matlab path carefully and see whether you accidentally added a (html?) file on it called open.m.
Lastly, you could try to use the built in open function directly, check doc builtin for this. If you succeed at least you are sure it is not a matter of corrupting the standard file.
im not sure what i did.. but i am working through some tutorials to get up to speed on python, and i started getting this error message... any ideas on how to fix this? from the error, i looked up the message, and it looks like wham i press the run button it is looking for a file that is no longer there.... but I'm not even working on that file anymore... I'm trying to run something different that does not refer to the previous file.
what does work is if i do run as.. but id rather not do that every time. I'm sure there is a setting I'm just not aware of that i messed up.
Well, not sure how exactly you're getting to that point from your explanation, but please take a look at: http://pydev.org/manual_101_run.html to see how to properly run a module inside PyDev.