java - WebView not working again after close -

-

I am trying to instantiate many GeFrames with WebVisse, it will work until the first web After this, at least one webview is still alive and JFRM (with everything else) is not settled.

After some investigation, it seems that after shutting down all WebVia JFrame, Platform.runLater () now next JFrame with immediate WebFiewPanel.

The following is the simplified code: 

  public class WebViewPanel {Private JFXPanel jfxPanel; Private webview view; Private web engine webengine; Private Jepynel Panel; Public WebViewPanel (JPanel Panel) {this.panel = Panel; Panel.setVisible (true); CreateScene (); } Private void createScene () {Platform.runLater (New Runnabal) {@Override Public Zero Run (Run) {// Runnable now goes after JFrames jfxPanel = new JFXPanel () with all WebFiewPanels; View = new WebView (); WebEngine = Vih. Gatienjin (); JeffPennell.Setsen (new view (see)); Panel.ed (jfxpanel); JFXPanel.Set (right);}}); }}

So, what should I do to solve this problem?

This happens because the platform exits itself, if not explicitly set.

Add 

  Platform.runLater (new Runnabel () {//   
 here  Platform.setImplicitExit (false) ;  first line 
 
 then your new code will be - 
 
  Private Zero Season () {Platform.runLater (New Runnab) (Platform.setImplicitExit ); @ Override Public Zero Run (jfxPanel = new JFXPanel;); View = New WebView;); WebEngine = view.getEngine (); jfxPanel.setScene (new view (see)); panel.edfxPanel; JfxPanel.setVisible (true);}})}}  
 
 FYI only if you are trying to display the panel more than once There is no need to make. Sken () Add JFXPanel to JFrame (preferi bleed panel also works fine with a constant reference) Set the frame to close it and then when you need to show it So set the same frame set whiSalele (true); Each time you call this frame you can also see that the static reference of this frame indicates zero (to represent the first call) If so, call CREATESCACEIN () and just set the constant reference for the visible.

Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more