The project i am working on is pretty big, with each Clean&Build and debug taking a lot of time, is there any way to netbeans to make any kind of sound or pop up, saying that the debug is finished? or the clean&build?
The current version of netbeans i have is 8.1. I appreciate if anyone knows
Not exactly what you are searching but there is a plugin for making sounds when a certain breakpoint is hit: http://plugins.netbeans.org/plugin/56682/beep
Maybe this is already sufficient for you.
Else writing your own plugin shouldn't be that hard.
Related
I am using Unity as a library for SwiftUI quite a while now. However when updating to the newest iOS version (16.1) it stopped working. Compiling runs without a problem but during runtime I get an error when Unity is starting:
in:
I even started a completely new project with Unity included to SwiftUI and get the same error. As this is some kind of assembler code and I certainly do not know how to read it I don't really know where I have to start searching.
In the console I get: "warning: UnityFramework was compiled with optimization - stepping may behave oddly; variables may not be available." I tried several ways to turn off optimization as described in related questions which did not work. When unchecking "Debug" in the scheme options the project starts normally
A similar thing happened to me. I'm not entirely sure if it's the same problem but in the console, I got a message saying UnityFramework is running optimized and may behave oddly. Unfortunately, I've tried a couple of ways to disable optimization but I've yet to find a solution.
For now, I'm able to bypass this error by disabling the debugger entirely. In order to do this, you have to go to Product -> Scheme -> Edit Scheme and uncheck debug executable.
I'm not sure if this will work for you but I figured it'd be worth a shot!
any advice how to eliminate this problem on this version? or any other advice?
Thank you.
Sometimes when I'm in the zone.. I forgot to remind myself not to ctrl+z while in the editor view of unity and worst case is every time it crashes it doesn't save my changes or update in the past 40mins-1hr work.
additional info: I am required to use the stated version.
update: as of the moment(12/4/2022), this issue is gone. I don't know how or why. I can do ctrl+z now in the editor mode.
This seems like a very isolated issue. I looked up crash reports and can only find it for older versions. I think that a clean reinstall would be your best bet but I 'am guessing you already tried that. Here are the only bug reports I found:
https://issuetracker.unity3d.com/issues/prefabs-and-undo-leads-to-crash
it is only on versions: (2017.2.0b3, 2017.1.0p1, 5.6.2p4, 5.5.4p2)
I have a really frustrating problem with eclipse PDT. When I am debugging I am getting exceptions all the time(which should not be there) I suspect the eclipse cached some of the files and this is the reason why I am getting those exceptions. I am sure that the code is correct at least where eclipse is throwing the exceptions since when I look at the code in NetBeans I can step over it without getting any exceptions whatsoever. There's a checkbox for symfony in NetBeans which can ignore the symfony cache and I guess that's why I am able to debug in there. However I very much like eclipse and I'd like to use it as a debuging and coding tool.
P.S.
I have cleared the symfony cached via cmd and tried again but I had no luck.
I am open to any suggestions that'd fix my issue, thanks!
P.S.2
I am using ecliplse luna and symfony 1.2
I know that it is too late, but I am posting the answer for any who might still struggle with this issue. The problem in my case was that in the debug view in eclipse I have had some variables that could not be resolved in the context when I was debugging (for example old variables that I have watched in other debug sessions). And when they were miscalculated eclipse's debugger had stopped responding. So if you have a similar problem my suggestion would be: first clear all previous variables from the debug view.
I have had this problems for a couple of times but usually could solve it by an update. However, this fix does not work for me anymore.
Actually, two problems here:
The minor one: I have osX 10.8.3 and Eclipse Juno (M20130204-1200) installed. Since a good amount of time, it takes eclipse ~ 4-5 minutes to start up for the first time after the system start. Once it was closed and is re-opend again, it starts up quick. I think this problem came since apple started to mess around with the JRE? Does anybody also experienced this delay? Could it be that one of the installed plugins checks for updates and causes the delay?
The major one: after eclipse is fully up & running, I can not open .py files anymore. When I open my pydev project (btw. pydev 2.7.3), eclipse freezes and I need to kill the whole thing and restart. -> I can not use it for python coding anymore, which is my primary task...
Suggestions? Re-install eclipse maybe?
Thank you for suggestions,
El
Can't really comment on #1, but for #2, can you try attaching jvisualvm to see what's going on there? (and create a thread-dump and post it somewhere so that I can take a look at it).
I'd ask you to create a bug-report for that, but the new tracker is still not up (I hope I'm able to put it up right after the funding at http://igg.me/at/liclipse is finished).
The problem was resolved by following these steps. They essentially disable one
JRE.http://support.apple.com/kb/HT5559?viewlocale=en_US
I'm a relatively new developer who uses the Force.com IDE on eclipse.
What are some things I could do to avoid this happening in the future? I heard that using Eclipse might not be the efficient way of doing things in general... but I'm very used to it.
Any hints/advice/guidance would be appreciated.
Was it a VF page that timed out? You need to figure out what's taking so long. Do you have an infinite loop, or inefficient loops that are chewing up thousands of statements executed?
Set up a log under Setup > Monitoring > Debug Logs and then run your script again. Check out the profiling and governor limit information at the bottom. It should give you an idea of where time is being spent.
If you are talking about callout then you can set higher timeout.
In Eclipse can be another type of timeout - during saving files. If you mean this then you should save file(s) one more time.
I'm working with SF for half a year and I have been using Eclipse for developing stuff. I can say that there are no problems with using it.
The issue resolved itself when I migrated to the stand-alone Force.com IDE.