summaryrefslogtreecommitdiff
path: root/framework/source/layoutmanager
diff options
context:
space:
mode:
authorTor Lillqvist <tml@iki.fi>2013-02-22 09:48:17 +0200
committerTor Lillqvist <tml@iki.fi>2013-02-22 09:58:19 +0200
commit616c6924f18911fce110918edf05ed2f4e52dba9 (patch)
tree3e307b3e91fe6b025701eb3dfea0ff61c750aff6 /framework/source/layoutmanager
parent7ca8407b403bf97a472ce2ade7e3fa1cb588cf24 (diff)
s/the the/the/
Change-Id: Iadacffaad832c6ff06757e8567e24f929f24a4c3
Diffstat (limited to 'framework/source/layoutmanager')
-rw-r--r--framework/source/layoutmanager/layoutmanager.cxx2
1 files changed, 1 insertions, 1 deletions
diff --git a/framework/source/layoutmanager/layoutmanager.cxx b/framework/source/layoutmanager/layoutmanager.cxx
index ece410cc8432..0da9cc032d77 100644
--- a/framework/source/layoutmanager/layoutmanager.cxx
+++ b/framework/source/layoutmanager/layoutmanager.cxx
@@ -2482,7 +2482,7 @@ sal_Bool LayoutManager::implts_resizeContainerWindow( const awt::Size& rContaine
if (( rContainerSize.Width > aWorkArea.GetWidth() ) || ( rContainerSize.Height > aWorkArea.GetHeight() ))
return sal_False;
// Strictly, this is not correct. If we have a multi-screen display (css.awt.DisplayAccess.MultiDisplay == true),
- // the the "effective work area" would be much larger than the work area of a single display, since we could in theory
+ // the "effective work area" would be much larger than the work area of a single display, since we could in theory
// position the container window across multiple screens.
// However, this should suffice as a heuristics here ... (nobody really wants to check whether the different screens are
// stacked horizontally or vertically, whether their work areas can really be combined, or are separated by non-work-areas,