Doxygen warnings corrected

* Doxygen spits out a lot of warnings about not being able to find
match function signatures, etc. This is because in some headers we
have a using namespace statement, in others it gets confused between
::Window and Window (!).

* Wrong use of tags:
+ Lots of @seealso - should be @see
+ Wrong usage of @overload - corrected with the right function
signature
+ HTML tags that doxygen doesn't recognize removed

Conflicts:
include/vcl/toolbox.hxx

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

1 files changed, 10 insertions, 6 deletions

diff --git a/include/vcl/outdev.hxx b/include/vcl/outdev.hxx
index 4f2243658c59..8a7c43938022 100644
--- a/include/vcl/outdev.hxx
+++ b/include/vcl/outdev.hxx
@@ -624,22 +624,26 @@ public:
     static OUString    GetNonMnemonicString( const OUString& rStr )
                             { sal_Int32 nDummy; return GetNonMnemonicString( rStr, nDummy ); }
 
-    sal_Bool                GetTextBoundRect( Rectangle& rRect,
+    sal_Bool           GetTextBoundRect( Rectangle& rRect,
                             const OUString& rStr, sal_Int32 nBase = 0, sal_Int32 nIndex = 0, sal_Int32 nLen = -1,
                             sal_uLong nLayoutWidth = 0, const sal_Int32* pDXArray = NULL ) const;
-    sal_Bool                GetTextOutline( PolyPolygon&,
+
+    sal_Bool           GetTextOutline( PolyPolygon&,
                             const OUString& rStr, sal_Int32 nBase = 0, sal_Int32 nIndex = 0,
                             sal_Int32 nLen = -1, sal_Bool bOptimize = sal_True,
                             sal_uLong nLayoutWidth = 0, const sal_Int32* pDXArray = NULL ) const;
-    sal_Bool                GetTextOutlines( PolyPolyVector&,
+
+    sal_Bool           GetTextOutlines( PolyPolyVector&,
                             const OUString& rStr, sal_Int32 nBase = 0, sal_Int32 nIndex = 0,
                             sal_Int32 nLen = -1, sal_Bool bOptimize = sal_True,
                             sal_uLong nLayoutWidth = 0, const sal_Int32* pDXArray = NULL ) const;
-    sal_Bool                GetTextOutlines( ::basegfx::B2DPolyPolygonVector&,
+
+    sal_Bool           GetTextOutlines( ::basegfx::B2DPolyPolygonVector &rVector,
                             const OUString& rStr, sal_Int32 nBase = 0, sal_Int32 nIndex = 0,
                             sal_Int32 nLen = -1, sal_Bool bOptimize = sal_True,
                             sal_uLong nLayoutWidth = 0, const sal_Int32* pDXArray = NULL ) const;
-    sal_Bool                GetGlyphBoundRects( const Point& rOrigin, const OUString& rStr, int nIndex,
+
+    sal_Bool           GetGlyphBoundRects( const Point& rOrigin, const OUString& rStr, int nIndex,
                             int nLen, int nBase, MetricVector& rVector );
 
     void                DrawPixel( const Point& rPt );
@@ -805,7 +809,7 @@ public:
         Theoreticaly, handing over a matrix would be needed to handle
         painting rotated EPS files (e.g. contained in Metafiles). This
         would then need to be supported for Mac and PS printers, but
-        that's too much for now, wrote #i107046# for this */
+        that's too much for now, wrote \#i107046# for this */
     bool                DrawEPS( const Point& rPt, const Size& rSz,
                                  const GfxLink& rGfxLink, GDIMetaFile* pSubst = NULL );