1. 16 Oct, 2017 - 6 commits
    • Tor Arne Vestbø's avatar
      macOS: Mark the widget's container as embedded when placed into NSMenuItem · ac35f9c4
      Tor Arne Vestbø authored
      
      Otherwise we'll end up creating a NSPanel for the QMacNativeWidget which is
      never closed, even if the backing NSView is moved to a new superview.
      
      Ideally this would be based on [NSView viewDidMoveToSuperview] and
      [NSView viewDidMoveToWindow], with retain/releases of the corresponding
      NSWindow, but that needs more research, especially as AppKit on macOS
      10.13 will always keep a strong reference to the NSWindow.
      
      Task-number: QTBUG-63443
      Change-Id: I9eec5ea871373d00dedf154600bf7005898cf37a
      Reviewed-by: default avatarMorten Johan Sørvig <morten.sorvig@qt.io>
      v5.10.0-beta2
      ac35f9c4
    • Tor Arne Vestbø's avatar
      macOS: Add support for non-window backed offscreen surfaces · ed9340a9
      Tor Arne Vestbø authored
      
      The modern approach to offscreen rendering on macOS is via FBOs, which
      means there's no reason to allocate an NSView and corresponding NSWindow
      just for that. In the offscreen case the NSOpenGLContext has a nil-view.
      
      Change-Id: I2d1d407069af4d5283e6f56fba83db8eaf694ac6
      Reviewed-by: default avatarLaszlo Agocs <laszlo.agocs@qt.io>
      ed9340a9
    • Timur Pocheptsov's avatar
      HTTP/2 protocol handler: tweak receive window sizes · a520c179
      Timur Pocheptsov authored
      
      We were using the default ones, provided by RFC7540. It appears they are way
      too restrictive and conservative: when downloading something relatively big,
      a stream keeps spending the whole session/its own 'recv' windows and thus
      we have to constantly send WINDOW_UPDATE frames. This significantly slows
      down our HTTP/2 implementation, making it orders of magnitude slower than
      HTTP/1.1. To fix this:
      
      - We send SETTINGS_INITIAL_WINDOW_SIZE in the first SETTINGS frame
        to inform our peer that per-stream WINDOW is bigger than 64Kb
      - We increase the session's receive window size.
      
      Task-number: QTBUG-63722
      Change-Id: I31312fcfd5f0fc0aee6aaa5d3562cc7d1b931adc
      Reviewed-by: default avatarEdward Welbourne <edward.welbourne@qt.io>
      a520c179
    • Thiago Macieira's avatar
      configure: make C++11 <random> a required functionality · 65eed6d5
      Thiago Macieira authored
      
      Error out if it's missing or broken (Mersenne Twister not present).
      
      This ensures that we never have a low-quality random generator in Qt.
      
      Change-Id: I0a103569c81b4711a649fffd14ec80649df7087e
      Reviewed-by: default avatarLars Knoll <lars.knoll@qt.io>
      65eed6d5
    • Edward Welbourne's avatar
      Don't lose precision in QMacTimeZonePrivate::previousTransition() · a090076e
      Edward Welbourne authored
      
      NSTimeInterval is a typedef for double, but the code stored its value in
      an int, and only then multiplied by 1000.
      
      Fix by only truncating NSTimeIntervals to int(64_t) *after* the
      multiplication by 1e3 to get milliseconds.
      
      While it's highly unlikely that a transition will have fractional seconds
      length, don't assume if you can just calculate the more exact result.
      
      Adapted-From: Marc Mutz <marc.mutz@kdab.com>
      Change-Id: I0911b9c945a94ca24c3dfb23ed6a849141076326
      Reviewed-by: default avatarJake Petroules <jake.petroules@qt.io>
      a090076e
    • Laszlo Agocs's avatar
      hellovulkantexture: Fix issues with new validation layer · 414c058c
      Laszlo Agocs authored
      
      Upgrading to a recent Vulkan SDK (e.g. 1.0.61) leads to getting
      a few previously unseen warnings from the validation layers.
      
      Fix these:
      
      vkDebug: ParameterValidation: 8: vkCreateSampler(): The
      samplerAnisotropy feature was not enabled at device-creation
      time, so the maxAnisotropy member of the VkSamplerCreateInfo
      structure must be 1.0 but is 0.000000.
      
      vkDebug: DS: 461375808: vkCmdPipelineBarrier():
      pImageMemBarriers[0].srcAccessMask (0x4000) is not supported by
      srcStageMask (0x1). The spec valid usage text states 'Any given
      element of pMemoryBarriers, pBufferMemoryBarriers or
      pImageMemoryBarriers must not have any access flag included in
      its srcAccessMask member if that bit is not supported by any of
      the pipeline stages in srcStageMask, as specified in the table of
      supported access types.'
      
      vkDebug: DS: 6: vkCmdDraw(): Cannot use image 0x7 with specific
      layout VK_IMAGE_LAYOUT_GENERAL that doesn't match the actual
      current layout VK_IMAGE_LAYOUT_SHADER_READ_ONLY_OPTIMAL.
      
      vkDebug: DS: 61: Descriptor set 0xc encountered the following
      validation error at vkCmdDraw() time: Image layout specified at
      vkUpdateDescriptorSets() time doesn't match actual image layout
      at time descriptor is used. See previous error callback for
      specific details.
      
      Change-Id: I1a3200221ac725c2fa661eff3ac075262b9355c2
      Reviewed-by: default avatarAndy Nichols <andy.nichols@qt.io>
      414c058c
  2. 15 Oct, 2017 - 1 commit
  3. 14 Oct, 2017 - 6 commits
  4. 12 Oct, 2017 - 2 commits
  5. 11 Oct, 2017 - 4 commits
  6. 10 Oct, 2017 - 2 commits
  7. 09 Oct, 2017 - 3 commits
  8. 08 Oct, 2017 - 1 commit
  9. 07 Oct, 2017 - 1 commit
  10. 06 Oct, 2017 - 6 commits
  11. 05 Oct, 2017 - 6 commits
  12. 04 Oct, 2017 - 2 commits
    • Tor Arne Vestbø's avatar
      macOS: Prevent backingstore image detach during color space assignment · 5b4cf7af
      Tor Arne Vestbø authored
      
      The call to CGImageCreateCopyWithColorSpace took a naked toCGImage(),
      which left the resulting CGImageRef without a release, causing the
      extra ref by toCGImage() to never be derefed, and a subsequent detach
      of the image data on the next paint event.
      
      Wrapping the call in a QCFType<CGImageRef> solves the problem. The code
      has also been moved directly into QCocoaBackingStore::flush(), as there
      is no need to keep the CGImageRef a member.
      
      A local autorelease pool has been added to QCocoaBackingStore::flush(),
      so that the NSImage used for blitting the backingstore is released upon
      exit of the function, thereby releasing the corresponding CGImageRef.
      
      Note that for layered mode, the QImage will still detach, as the view's
      layer.contents property keeps a reference to the image data until being
      replaced in a subsequent flush.
      
      Task-number: QTBUG-63559
      Change-Id: I06b9298f65a84deae7cc2eff617ba75c92ec3b87
      Reviewed-by: default avatarMorten Johan Sørvig <morten.sorvig@qt.io>
      v5.10.0-beta1
      5b4cf7af
    • Tor Arne Vestbø's avatar
      iOS: Bump deployment target to 10.0 as planned for 5.10 · 1b473ee6
      Tor Arne Vestbø authored
      
      [ChangeLog][iOS] The minimum deployment target for applications is now
      iOS 10.0.
      
      Change-Id: Icb37e4eaecbf6f62fd3c9293b2abf19a0954a02d
      Reviewed-by: default avatarJake Petroules <jake.petroules@qt.io>
      1b473ee6