I've just migrated from Eclipse to JetBrains IntelliJ IDEA and I find it very annoying when it comes to using designer. When I create a new GUI form the designer works fine for some time. Then suddenly after switching to other class or after closing and reopening IntelliJ it shows me XML code only and I have no option to switch to designer mode. This time I have form with three buttons and IntelliJ shows me XML with three notifications at the top "missing mnemonic: name_of_a_button" despite that I didn't use any and never wanted to. By the way even if it works fine I don't have that switch at the bottom to toggle between designer and text mode. Why is that?
We have two options:
(1) Disabling this particular inspection by clicking the icon at the right of the message;
(2) Going to the button's Component Properties panel, "Text" property,clicking on the lamp icon and providing a mnemonic for the text. (image berllow)
I am running a page that launches a Java Webstart app and a Java Applet. I don't have problem launching this page in Firefox, but I have to run it in IE11. The thing is IE11 keep redirecting me to oracle java download site. I have install Java RE like 3 times from IE already. What am I missing?
This is the site i am having problem with: http://qa4.kiosk.ieventstest.com/
I got same issue on Jira when I was trying to attached an image. You can follow steps below:
Open IE >> Internet Options >> Security tab >> "Local Intranet"
Click on "Sites" button and UNcheck the checkbox "Auto detect intranet network" and CHECK all other 3 checkboxes underneath
Click "Advanced" button, and "Add" this website to the zone (if there is something on text box)
GOOD LUCK! :)
I recently tried to open a JPanel form that I created with NetBeans GUI Builder and NetBeans almost freezes up on me. The design form is an all-gray background, not the usual gray area where I can place components surrounded by a white background. If I click on the Source button and then switch back to Design view, all of the tabs in the editor pane disappear.
Fortunately I am using Git for version control. The last commit of this file was over a week ago. I might have to revert to an earlier version to see where this problem was introduced. In the mean time, does anyone have any idea what could cause this behavior? Is it possible that my .form file is corrupted? The application compiles and runs just fine.
It sounds like Netbeans can't load the form due to some internal error. This can sometimes be fixed by doing a clean & build to clear out any old cached data.
If that doesn't work, you can check out the "message.log" for the error...and yes, I wish it would display it on the screen
Off memory it use to be in "{user.profile}/.Netbeans/{version}/var/log" (I think). It got moved on Windows under 7.2 to "{user.profile}\AppData\Roaming\NetBeans\7.2\var\log"
I have an application where I need to be able to log out and the only way to do so is to click on the Log out option in the drop down menu however I am having a lot of problems.
I have captured the screenshots using the Sikuli IDE and when I run my code from the IDE it works perfectly fine. (The code clicks on Menu and then Log out)
However when I try to run the code from Java it appears that it selects Menu and then when it tries to click Log out, the menu disappears.
My guess is that for some reason Java is putting the focus on the mouse before it moves to the Log out button and when the focus goes to the mouse the menu disappears as it does when you click elsewhere.
I have also tried making Sikuli press the down button several times to get to log out but the same thing happens when it tries: the menu disappears.`
This is my Java code. The Sikuli code has the same two click commands:
#Override
public void logout()
{
click("loggedInIndicator.png");
click("logoutButton.png");
}
Please help! There is no other way to log out that I can find.
I suggest you to print the image Sikuli finds to be the best match for the elements. My guess is it selects a part of the screen that has nothing to do with the element you want to click on, making the menu disappear.
Match element = region.find("loggedInIndicator.png")
Screen screen = element.getScreen()
String imagePath = screen.capture(element)
This saves an image of the element found by Sikuli in the System temp directory. As it is a temporary file, you'll certainly have to move the freshly created image file to another directory so that it'll not be deleted immediately. I found this happening several times on Windows
OK, maybe I'm dumb/blind, but in the docs it says "rebuild and restart the server." But I don't see a button to do this anywhere. Or from any contextual menu. And I can't find anything in their docs explaining how to do it. If I just try to start the app again, it gets angry because I already have App Engine running on the needed port.
Only solution I've found is to restart Eclipse... any other ideas? A screenshot of a button would help if possible. :)
In eclipse, there is a view that contains your Console. If you click on that, you will see the STDOUT and STDERR output of your running application. In the upper right, there should be a red box that will terminate the currently running program.
I have a different and possibly more productive solution for you. Like with most web development environments you probably want to change your source code and have Google Appengine server reload the new code for you.
You need some version of the traditional "touch" unix command (if you work on windows you can download a version from here).
Then go to you project properties, Builders and add a new build step as a "Program". Under "Location" enter the path to your "touch" command ("D:\bin\UnxUtils\usr\local\wbin\touch.exe" for example - on Posix systems just "touch" should be enough since it's already in your PATH) and in "Arguments" put something like "${project_loc}/war/WEB-INF/appengine-web.xml".
Also go to the "Build Options" tab and check "During auto builds".
"touch" will update the timestamp in you appengine-web.xml. When the App Engine server detects changes to you appengine-web.xml it will reload the app automatically. The load process is very fast so it can be done whenever you change any file in your project (which normally triggers the auto-build in Eclipse) - you can tweak the builder to only run when you change certain types of files.
I might add that the "little red box" is not always visible. It drove me crazy reading that same instruction but not seeing the terminate button until I discovered that the Console windows has "layers" that you can select from using the drop-down button on the far right of the controls for the Console view. You just need to go "back" to the console screen that says the server is running and you will see the little red terminate button.
The previous answer wasn't cutting the cheese for me. Upon first starting App Engine, the red square would be available above the text entry area. If I then clicked the run button again, then red square would go away and the console for the previous launch would be replaced by the console for the new launch. To manually stop the App Engine server, you can kill it from the terminal:
http://geekbrigade.wordpress.com/2009/02/26/how-to-find-and-kill-a-process-that-is-using-a-particular-port-in-ubuntu/
In short, "sudo netstat -lpn |grep :8888" and kill the service by process ID.
Strangely, adding Google Web Toolkit to the project made my App Engine launch show up in the Development Mode pane, where it could be easily be killed or restarted.
Just Click on Debug perspective (should be on upper right panel), select the instance of web application on Debug panel (if you don't show it, you could enable by menu Window->show view->Debug) and click on red box of view menu.
The best I've found is to setup the keyboard shortcuts for the console's terminate button, and the run/debug start/restart command. By default, you can enable Command-F2 to terminate, and Command-F11 to restart, its fairly painless. Make sure to enable the full debug menu group (click on main toolbar -> customize, etc)
If you include the gwt SDK in your project, the gwt development mode box contains a reload server button that will work just fine.