This only happens in Mac
In the JavaFX Application if I displayed a ContextMenu or MenuItem the JXBrowser thread stops loading the webpage and when I dismiss them the page continue loading.
How can I avoid the JXBrowser thread stop loading a web page and interacting with JavaFX?
I'm currently using JXBrowser 6.9 but this also happens in previous versions.
When you use JxBrowser in heavyweight mode on Mac, the underlying Chromium engine runs inside Java process and uses the same AppKit thread as JavaFX. In case something blocks this thread, the Chromium engine is also blocked. I recommend that you use lightweight mode and multi-process architecture by setting "jxbrowser.ipc.external=true" VM parameter on Mac.
Related
I use Qt 5.7 with Web Engine in my application. The application has thousands of users and for some of them the whole application crashes (with the classic Windows "app.exe has stopped working" dialog) when trying to load a webpage in my webview. Upon doing some digging, I discovered it crashes for users that don't have OpenGL 2+.
Is there a way to determine the user's OpenGL version and shut down the application (or write a message to them, I'd take care of that) if the version is not supported? I tried using glGetString(GL_VERSION), but that means including yet another QT library in an already not so small application.
Does everybody know how to apply fullscreen exclusive mode for JavaFX desktop application? Because when application is running and some message appears on the screen (for example, network connection aborted), my application looses fullscreen mode :(
As a last resort i think you can kill the Explorer (on Windows) on app startup and restart it when you quit. Although I do think this is in
Im trying to launch a dialog by invoking several methods from a windows forms assembly. My app is a console app. All the execution logic goes well and without exceptions, but the window is not launched. Is it a known issue that you cant launch a windows form from a console app?
well, yes. You have to have a Windows message loop for this to work.
If you create a Forms application from scratch, you'll see the Program.cs module created with ... Application.Run(new YourMainForm()) in it. Run is basically the message pump - having that is pretty much a requirement for forms to work.
I develop Flex-Java applications which is running under Apache Tomcat. I use Flex Builder plug-in for Eclipse as my IDE. My application consists of several libraries and modules. I manage all of them as a small maven (flex-mojos) projects.
Does anybody can share some ideas how to setup robust debuging enviroment?
I use Maven & Flexmojos from the command line and the Flash builder 4 plugin inside of Eclipse. In my project I also have a Java/BlazeDS backend I like to debug at the same time as the Flex client on occasion.
Here's what I do:
1) I used cargo to startup an instance of my Java backend that DOES NOT have the SWF or HTML wrapper in it.
2) I've created a "Web Application" debug launch configuration where the launch URL just points to a file (e.g. "/path/to/my/flash-builder/bin/myapp-wrapper.html").
3) When I launch this debug configuration from within Eclipse the Flex debugger Just Works. As soon as a stop point it opened the Flex Debugger perspective automatically opens.
By launching a debug configuration directly from Eclipse I don't have to rebuild and redeploy a WAR file after each change made to the Flex app. In fact, after I shut down the Flex client I just leave the Java server running and reconnect with the next debugging launch.
In order debug the Java side, I start the application server with the JVM debugger command line arguments and launch a Remote Java Debugger debug launch configuration. Eclipse has no problem running both debuggers at the same time.
The only problem with this setup happens when I need to run the Flex web app from an http:// URL (for example to get flashvars to retrieve URL query parameters). In this case it is a long round-trip to get maven to created the WAR and deploy it, then to launch the debugger...after every Flex client source edit. I posted a question on how to make that case better (http://stackoverflow.com/questions/4426053/quickly-debug-flex-java-web-application-from-eclipse).
This is an area of interest to me so let me know what you are looking for and I can probably help more.
I'm using the AIR update framework (ApplicationUpdaterUI), and whenever the user updates the application, a new desktop icon gets created (overwriting any existing desktop icon there). Is there a way to suppress this behaviour, or can someone suggest a workaround?
Here's the situation:
Our AIR app uses a separate bootstrapping application to launch some services before the AIR application launches, so it's important that the user does not run the AIR executable themselves. Our installer creates a desktop icon that points to the bootstrapping executable. When the user updates the application, it replaces our desktop icon with the AIR shortcut.
I don't think you can override the creation of the standard AIR icon..
Maybe you can configure your helper application as a windows service / unix daemon, launching it automatically on system startup?