{"push_id":967457992,"size":1,"distinct_size":1,"ref":"refs/heads/2.0.x","head":"31bf5ab70aca01a710b64761c18e2ccfb5165da2","before":"261dca1aa22d849298c6cc17ab6c616090953845","commits":[{"sha":"31bf5ab70aca01a710b64761c18e2ccfb5165da2","author":{"email":"83dd9d6af43f8cbee08acd981417321e144b776b@virtualgl.org","name":"DRC"},"message":"Win/Java: Speed up creation of viewport window\n\nThe Java TurboVNC Viewer on Windows, when running under Java 7 and\nlater, took an inordinate amount of time to create the viewer window\nafter connecting to a VNC server.  This slowdown was due to a slow Win32\nsystem call-- DescribePixelFormat()-- which is used in the\nimplementation of GraphicsDevice.getConfigurations() in Windows JVMs\n(refer to https://bugs.openjdk.java.net/browse/JDK-6477756).  This\nsystem call also forces the DirectDraw DLL to be loaded, which is\nunnecessary (TurboVNC explicitly disables DirectDraw blitting for\nperformance reasons.)\n\nThe Java TurboVNC Viewer now automatically sets the sun.awt.nopixfmt\nsystem property to \"true\", which should significantly speed up the\ncreation of the viewer window, particularly on multi-screen clients, by\navoiding the slow DescribePixelFormat() system call.  This causes Java\n2D to always use the default pixel format for the display, but since the\nTurboVNC Viewer will always try to use GDI blitting (as opposed to\nOpenGL or DirectDraw blitting), the default pixel format should always\nwork.  If for some reason it doesn't, however, then the old behavior of\nthe Java TurboVNC Viewer can be restored by passing -Dsun.awt.nopixfmt=0\nto java or adding \"-Dsun.awt.nopixfmt=0\" to the JAVA_TOOL_OPTIONS\nenvironment variable.\n\nNote: Java apparently treats any value of sun.awt.nopixfmt as true,\nwhich is why the code in VncViewer.java has to clear the property in\norder to unset it.\n\nFixes #33","distinct":true,"url":"https://api.github.com/repos/TurboVNC/turbovnc/commits/31bf5ab70aca01a710b64761c18e2ccfb5165da2"}]}