tdf#88941 Revert "vcl quartz: Add support back for DXArray tweaking"

This reverts commit 4a0cb642.
MacOSx only (more exactly CoreText only)
The handling of DXArray was buggy and need to be re-worked
so this revert to the previous case where DXArray are esssentially
ignored at the char level and only kept at the fragment size level
and used to redistribute space in a fragment

This create some issue too but on more esoteric case than
the one noticed in tdf#88941

Change-Id: Icb33d0600267c3136f3a6b15de8ecd739898ce04
Reviewed-on: https://gerrit.libreoffice.org/16753Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>

vcl/quartz/CTRunData.cxx

@@ -17,7 +17,6 @@ CTRunData::CTRunData( CTRunRef pRun, int start)
     : ownership_flags(0)
     , m_StartPos(start)
     , m_pRun(pRun)
-    , m_pAdjPositions(NULL)
 {
     assert(pRun);
 
@@ -87,7 +86,6 @@ CTRunData::~CTRunData()
     {
         delete [] m_pPositions;
     }
-    delete [] m_pAdjPositions;
 }
 
 /* vim:set shiftwidth=4 softtabstop=4 expandtab: */

vcl/quartz/CTRunData.hxx

@@ -32,7 +32,7 @@ public:
     const CGPoint* m_pPositions;
     const CGSize*  m_pAdvances;
     const CFIndex* m_pStringIndices;
-    CGPoint* m_pAdjPositions;
+
     CTRunData(CTRunRef pRun, int start);
    ~CTRunData();
 };