Error in loading component: [JFrame]->Panel - Java NetBeans - forms

So its been a while since I last touched the GUI for this application. Today I tried to open the main form and got this error message:
Note everything compiles/runs perfectly, I get no errors whatsoever.

It might be because you used to have a custom GUI window/panel/component and you modified that class. Now the IDE does not recognize it anymore, so just press "Not editable" button when NetBeans Shows you the dialog, then perform a "Clean and Build" (the broom and hammer icon). After build completes close and reopen the IDE. It worked form me.

It an error that append sometimes when you switch from a version to an other. I get the same issue, I got the message but all run well.
If you want more informations about the problem encoutered, go in :
(In the menu bar) View -> IDE Log
here you should see the details of the error when you get this Warning window.

Related

Go to next compiler error across project in IntelliJ

I spend a lot of time going back and forth between SBT and IntelliJ, getting a file, line number, and error from SBT and navigating to it in IntelliJ. Is there a way to automate this at all? Even if it's only via IntelliJ's compiler, I'd love to be able to navigate to the next error project-wide.
To navigate between errors or warnings in IntelliJ you can do one of the following:
Use keyboard shortcuts F2 (Next) and Shift+F2 (Previous) respectively.
On the main menu, choose Navigate | Next / Previous Highlighted Error.
I am using Ctrl+Alt+Up/Down to scroll through the list of errors. This is inside the Compile Messages window. The SBT Console uses the same shortcut, as stated in the SBT wiki.
For this specific question, just use F2 (Next) and Shift+F2 (Previous);
But for any other questions related to shortcuts of IDEA, searching in the Settings-Keymap is better than in Google.
To go to next compilation error in the next file:
Command-0 (go to messages tab where compile errors are)
Down arrow until get to next error
Enter
Esc to get to back to code where this error is
The highly voted answer has not really answered the question. The provided solution of F2 only navigates through the errors in the current file. But picking up from the comments, the suggestion below is not the ultimate answer but is a little bit closer.
Select Problems as shown in the image below
This will list all files that have errors.
Use F2 to navigate through the errors.
At least with this method, it has narrowed down the files with the errors and are just a click away.
2022 UPDATE
This is a whole project, error to error, one-click solution after a 2-second setup. For both setups, optionally disable generate warnings for your compiler.
Windows/Linux Setup
Alt6 or click Project Errors tab of Problems tool window
CtrlNumPad+ or click
to expand all errors
MacOS Setup
Cmd6 or click Project Errors tab of Problems tool window
Cmd+ or click to expand all errors
Now click the first error in the Project Errors tab, fix it, then click the next error. Works regardless of build tool and may work in older versions of intellij than 2022.1.
Edit: Credit #Manuel Romeiro - the answer in his comment worked for a while, but stopped when intellij got confused somehow. Will update my answer if I figure that out.
Thanks #meridsa for providing setup step 1 for Mac. Also to #K. Symbol for syntax for showing keys in an answer (very cool).
For the mac I couldn't find anything that worked until I discovered the following
cmd + 1 -> f2 (on files) -> escape -> f2 (inside file) -> cmd + 1 -> repeat
For going to the next error across the entire project, use Alt+F2 instead of just F2.
On Mac, you can enable Fn regular key functionality in System Preference.
Choose Apple Menu > System Preferences.
Click Keyboard & Mouse.
Click the Keyboard tab.
Select the option Use All F1, F2, Etc. Keys As Standard Function Keys.
Quit System Preferences.

Disable Netbeans exception report window

I need to disable the "Exceptions" window that pops when you encounter an IDE error in Netbeans - I always report when I can but is driving me crazy right now.
Don't get me wrong, I love the application, but I'm getting tired of the errors on my screen, sometimes needing to delete a file and create him again to enable me to continue.
I can drag it to the side but my mouse loses focus.
I'm using Windows 7 and latest version of Java (netbeans PHP ide)
Is this possible?
You need to modify <netbeans-install-dir>/etc/netbeans.conf
Add
-J-Dnetbeans.exception.alert.min.level=99999 -J-Dnetbeans.exception.report.min.level=99999
to the netbeans_default_options entry.
You have to set some properties when launching Netbeans. Modify your application configuration in "nbproject/platform.properties" by finding a line run.args.extra=... and adding at the end:
-J-Dnetbeans.exception.alert.min.level=99999 -J-Dnetbeans.exception.report.min.level=99999
You'll find the details in Netbeans' wiki.
I would recommend using -J-Dnetbeans.exception.report.min.level=99999 but not the other one. This means the error icon will still appear when there is a problem, and you can report the error if you have a moment, but no dialog will pop up without your asking it to.

Debug in Eclipse - ClassNotFoundException

when i debug in Eclipse a simple console application, I get a lot of ClassNotFoundException lines in the debug Window. It is not an error, somewhat lower in another pane I get "Source not found.". I understand that it is because the source code of the required class is not available, buI would like to skip over these lines... I have to press a lot of times the "step over" or "step out" button to get out of these states.
What can I do in order to avoid these useless lines at all?
Thanks
I've been having this problem for a few months now. I'd be debugging a java app and every time I'd hit a constructor, eclipse would try to find matching java core library ClassNotFoundException's source code.
I solved this problem by right-clicking in Debug window on the ClassNotFoundException when I hit it, and clicking on Filter Type. I would then right-click in the debug window again and choose Edit Step Filters.... In the Edit Step Filters window I checked everything in the Defined Step Filters section and unchecked everything in the bottom of the window (Filter synthetic methods, Filter static initializers, etc).
Hope this helps others in the future.
After Launching Debug Mode.
Go to Window → Show View → Break Points.
Now you would be able to see Break Point tab in Debugging mode.
Uncheck the option "ClassNotFoundException: caught and uncaught".
While debugging try Step Return (F7 as shortcut) to get one level up at a time and thus out of the libs you don't have the source attached for.
In a normal application your own code (your java files) is mixed together with code of others (class files in libraries, runtime environment, etc.).
Each time you step into a class file you will get this "Source not found"-Warning. (as you already mentioned in your question)
At first you could try to get the source codes for the libraries and link them to your libraries (for example in "project setup => Preferences.../Java Build Path/Libraries => unfold a jar-libraries => Source attachment").
If no source code is available you have to use the debugger-comands to avoid jumping into that class files. "Step Out/Return" might help, but the "Debug View" (which can be found in the top left corner in your "Debug Perspective") could be even more helpful.
In the "Debug View" you can see each thread of your application. If you are currently debugging a thread you can there see the current stacktrace. Instead of clicking F6 and F7 all the time you can also navigate by clicking on an stacktrace-item there.
Tipp: I am using - (Rightclick->"run to line") a lot - this is quite helpful to run over loops, etc.
An occurence of ClassNotFoundException is most common in debugging in order to avoid these exceptions, In breakpoints window(Windows>Show View>BreakPoints) uncheck the "ClassNotFoundException: caught and uncaught" to continue with the normal debugging.

Any way to stop Eclipse CDT build?

I'm attempting to build a project in Eclipse CDT and the build process fails early on, but then takes minutes to finish computing and finally quit.
How, through the Eclipse IDE, can I stop the build process.
I know there must be some way because I can delete any random file from the Project Explorer and a box pops up with the processes and I can click the red box next to build and it quits. But I shouldn't be required to delete a random file to get that box to pop up. Where is it?
There is a "progress view" found at Windows->Show View->other->General->Progress. That has the little red square I need to stop any particular task.
FYI - there's also a setting in the Properties sheet to "Stop on first build error".
Under the C/C++ Build item in the Properties page, click on the configuration you wish to modify, choose the Behavior tab, and click the checkbox under "Build Settings" ("Stop on first build error").
You can still use John's method to stop the build at any time, but if you're looking to have the build stop when you first encounter an error instead of continuing on, this setting might be helpful.
I use -Wfatal-errors flag in Makefile in Eclipse to prevent polluting my console
-Wfatal-errors
This option causes the compiler to abort compilation on the first error occurred rather than trying to keep going and printing further
error messages.
https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Warning-Options.html
You can disable the console's annoying focus-stealing behavior both for the build messages (so you can get the progress dialog to stay open) and for your program's console output (when debugging multiple threads). Go to window->preferences->C/C++/Build/Console and you'll find an option "Bring console to top when building (if present)". Uncheck that and you then can pause the build as you wish. To keep your program output chilled you can go here: http://georgik.sinusgear.com/2011/12/22/how-to-disable-stealing-of-focus-by-console-in-eclipse/

Annoying error dialog box when eclipse output-console scrolls. What's causing it?

When I run python scripts in Eclipse with Pydev - after a few seconds I get an eclipse Error dialog.
The window title is "Multiple Problems have occurred".
The box has a red X icon, adjacent to an error message "An internal error has occurred"
The list of error windows all have the text "Reveal End of Document". If I click on details I get the follow-on message
An internal error has occurred.
39
This problem seems to be related to the console. I've noticed that the scroll-bar is missing. I can sometimes scroll using the arrow keys, however scrolling occasionally causes the console area to mess up. I've googled that "Reveal End of Document" is supposed to be an exclipse IDE function which ought to cause a console to jump to the end.
Does anybody have an idea what might be going on? How can I fix this problem? It's really annoying.
Using Eclipse 3.6 on an up to date Sun JDK with Pydev plugin on Windows XP 32 bit.
This seems to be related to Eclipse Bug 243877 - IOConsole Updater error with long output lines
I am not using Pydev but I have been getting a lot of these "Reveal End of Document" popups and "org.eclipse.text" exceptions.
As mentioned in the bug report, it is directly related to the "Fixed width console" check box in Eclipse Preferences -> Run/Debug -> Console. When I checked the box and got too long message in my console, the exceptions flooded in. As soon as I unchecked the box, it stopped.
Can't believe its still here in Indigo.
Just Uncheck Fixed width console.
Yes, this answer sounds weird, But it worked for me.
Hope this helps.
See this bug which looks related.
What worked for me: Closing all windows and views.
Right click on a source tab -> Close All. Do the same for Views. Re-run application. Console automatically opens with output with no annoying error popup.
It happens when your program exceeding the console width.
If you clear the console, the message box stop.
Right click and clear console (also when it's running).