1. 17 May, 2019 3 kayıt (commit)
  2. 16 May, 2019 4 kayıt (commit)
  3. 15 May, 2019 6 kayıt (commit)
  4. 14 May, 2019 3 kayıt (commit)
  5. 11 May, 2019 3 kayıt (commit)
  6. 10 May, 2019 3 kayıt (commit)
    • Eike Rathke's avatar
      Resolves: tdf#125099 round duration results in interpreter already · f01e3176
      Eike Rathke yazdı
       This is a combination of 3 commits.
      
      Resolves: tdf#125099 round duration results in interpreter already
      
      So wall clock time formats less likely display a one-off value,
      duration formats are too rarely used if the expected duration is
      less than 24 hours.
      
      Reviewed-on: https://gerrit.libreoffice.org/71909
      Tested-by: Jenkins
      Reviewed-by: 's avatarEike Rathke <erack@redhat.com>
      (cherry picked from commit 85c0521f)
      
      Test RANK(), not the underlying floating point representation of duration
      
      The RANK() results depended on the floating point representation
      of time differences (durations), which for visually equal MM:SS
      display values don't have to be equal if similar durations result
      from different start and end times. Change that to a well defined
      duration in seconds.
      
      b69a6b43f48abd2d4fe605021acfd2800e75b5e1
      Reviewed-on: https://gerrit.libreoffice.org/71926Reviewed-by: 's avatarEike Rathke <erack@redhat.com>
      Tested-by: Jenkins
      (cherry picked from commit 8de79490)
      
      Fix typed flags bitmask, tdf#125099 follow-up
      
      25327cfcafc9e1f2e88b388677853c638dd9b0e6
      Reviewed-on: https://gerrit.libreoffice.org/71946Reviewed-by: 's avatarEike Rathke <erack@redhat.com>
      Tested-by: Jenkins
      (cherry picked from commit d27ad84e)
      
      Change-Id: I9b0872420699b17e3ed3f20993f8cfe02761f862
      Reviewed-on: https://gerrit.libreoffice.org/71935
      Tested-by: Jenkins
      Reviewed-by: 's avatarCaolán McNamara <caolanm@redhat.com>
      Tested-by: 's avatarCaolán McNamara <caolanm@redhat.com>
      f01e3176
    • Michael Stahl's avatar
      tdf#124675 sw: fix crash when moving SwTextFrame in table to prev page · 232b4670
      Michael Stahl yazdı
      The problem is that the SwTabFrame and SwRowFrame that are being
      iterated are deleted:
      
       7 SwFrame::DestroyFrame(SwFrame*) (pFrame=0x79052c0) at sw/source/core/layout/ssfrm.cxx:386
       8 SwTabFrame::RemoveFollowFlowLine() (this=0x5bf07d0) at sw/source/core/layout/tabfrm.cxx:907
       9 SwTabFrame::MakeAll(OutputDevice*) (this=0x5bf07d0) at sw/source/core/layout/tabfrm.cxx:1839
      10 SwFrame::PrepareMake(OutputDevice*) (this=0x5bf07d0) at sw/source/core/layout/calcmove.cxx:344
      11 SwFrame::Calc(OutputDevice*) const (this=0x5bf07d0) at sw/source/core/layout/trvlfrm.cxx:1790
      12 SwFrame::PrepareMake(OutputDevice*) (this=0x603a570) at sw/source/core/layout/calcmove.cxx:247
      13 SwFrame::Calc(OutputDevice*) const (this=0x603a570) at sw/source/core/layout/trvlfrm.cxx:1790
      14 SwFrame::PrepareMake(OutputDevice*) (this=0x5daf120) at sw/source/core/layout/calcmove.cxx:247
      15 SwFrame::Calc(OutputDevice*) const (this=0x5daf120) at sw/source/core/layout/trvlfrm.cxx:1790
      16 SwFrame::PrepareMake(OutputDevice*) (this=0x6005ca0) at sw/source/core/layout/calcmove.cxx:247
      17 SwFrame::Calc(OutputDevice*) const (this=0x6005ca0) at sw/source/core/layout/trvlfrm.cxx:1790
      18 SwFrame::MakePos() (this=0x6094330) at sw/source/core/layout/calcmove.cxx:490
      19 SwTextFrame::MakePos() (this=0x6094330) at sw/source/core/text/frmform.cxx:343
      20 SwContentFrame::MakeAll(OutputDevice*) (this=0x6094330) at sw/source/core/layout/calcmove.cxx:1346
      21 SwFrame::OptPrepareMake() (this=0x6094330) at sw/source/core/layout/calcmove.cxx:368
      22 SwFrame::OptCalc() const (this=0x6094330) at sw/source/core/inc/frame.hxx:1060
      23 SwLayAction::FormatLayout(OutputDevice*, SwLayoutFrame*, bool) (this=0x7ffc6da48350, pLay=0x8a349c0, bAddRect=false) at sw/source/core/layout/layact.cxx:1362
      24 SwLayAction::FormatLayout(OutputDevice*, SwLayoutFrame*, bool) (this=0x7ffc6da48350, pLay=0x79052c0, bAddRect=false) at sw/source/core/layout/layact.cxx:1357
      25 SwLayAction::FormatLayoutTab(SwTabFrame*, bool) (this=0x7ffc6da48350, pTab=0x7a9c300, bAddRect=false) at sw/source/core/layout/layact.cxx:1569
      26 SwLayAction::FormatLayout(OutputDevice*, SwLayoutFrame*, bool) (this=0x7ffc6da48350, pLay=0x7c30300, bAddRect=true) at sw/source/core/layout/layact.cxx:1354
      27 SwLayAction::FormatLayout(OutputDevice*, SwLayoutFrame*, bool) (this=0x7ffc6da48350, pLay=0x79e1780, bAddRect=true) at sw/source/core/layout/layact.cxx:1357
      28 SwLayAction::InternalAction(OutputDevice*) (this=0x7ffc6da48350) at sw/source/core/layout/layact.cxx:546
      
      They are deleted because the last SwTextFrame was moved via MoveBwd() to
      the previous page, and is formatted there.
      (regression from commit 18765b9f)
      
      Prevent this via:
      
      * delete-guard for the SwRowFrame - causing RemoveFollowFlowLine() to
        return early (also, let it return false, so the Join() isn't even
        called, although that doesn't make a difference in practice because
        of the next item:)
      
      * join-guard for the SwTabFrame - otherwise tabfrm.cxx:2199 will Join()
        it anyway
      
      This means that when the page with the follow-frame is done formatting,
      the empty SwTabFrame with no SwTextFrame in it will remain.  Fortunately
      this is not a problem, because due to the moving, the previous page will
      be invalid and layact.cxx:613 will iterate to the previous page and
      format it again; then tabfrm:2199 of the master SwTabFrame will detect
      that the follow SwTabFrame is empty and Join() it.
      
      Change-Id: I2cca89d63b81e7d4909319fa4feab2f5d67a6ff3
      Reviewed-on: https://gerrit.libreoffice.org/71996
      Tested-by: Jenkins
      Reviewed-by: 's avatarMichael Stahl <Michael.Stahl@cib.de>
      (cherry picked from commit cc5916cd)
      Reviewed-on: https://gerrit.libreoffice.org/72031Tested-by: 's avatarXisco Faulí <xiscofauli@libreoffice.org>
      Reviewed-by: 's avatarMiklos Vajna <vmiklos@collabora.com>
      232b4670
    • Miklos Vajna's avatar
      tdf#124594 DOCX filter: don't extend margins from effects for rotated shapes · da5f9c68
      Miklos Vajna yazdı
      Regression from commit a5a836d8 (DOCX
      filter: effect extent should be part of the margin, 2014-12-04), the
      problem was that extending margins as-is based on the effect extent
      values only work correctly in case of non-rotated shapes.
      
      For example, with 90 degree clockwise rotation the top effect extent
      should extend the right margin, etc. Fix the bug by limiting this
      extension to the non-rotated scenario.
      
      Test the behavior at a layout level, so in case later the effect extent
      feature is implemented, it won't be necessary to adjust the test.
      
      (cherry picked from commit 65420c21)
      
      Conflicts:
      	sw/qa/extras/ooxmlexport/ooxmlexport13.cxx
      
      Change-Id: I97271bbb7c079951980b436cb8d8e5e54eeead55
      Reviewed-on: https://gerrit.libreoffice.org/71893
      Tested-by: Jenkins
      Tested-by: 's avatarXisco Faulí <xiscofauli@libreoffice.org>
      Reviewed-by: 's avatarMichael Stahl <Michael.Stahl@cib.de>
      da5f9c68
  7. 09 May, 2019 2 kayıt (commit)
  8. 08 May, 2019 6 kayıt (commit)
  9. 07 May, 2019 4 kayıt (commit)
  10. 06 May, 2019 3 kayıt (commit)
  11. 04 May, 2019 2 kayıt (commit)
  12. 03 May, 2019 1 kayıt (commit)