summaryrefslogtreecommitdiff
path: root/vcl
diff options
context:
space:
mode:
authorTor Lillqvist <tml@collabora.com>2014-04-23 08:19:08 +0300
committerTor Lillqvist <tml@collabora.com>2014-04-23 08:22:02 +0300
commitf420a49a76030b0cf4b38ba13f9630c212bc6418 (patch)
tree483148fd34b4722be183c3302af569b4f0d5181e /vcl
parenta26d592dab62842b97d25045ce8f88a9c068dc97 (diff)
Fix typo: s/potentioal/potential
Change-Id: I13eecb1d4f79ec022228a95f9ce18ed667e4ef3f
Diffstat (limited to 'vcl')
-rw-r--r--vcl/win/source/gdi/salgdi.cxx2
1 files changed, 1 insertions, 1 deletions
diff --git a/vcl/win/source/gdi/salgdi.cxx b/vcl/win/source/gdi/salgdi.cxx
index 9cb39cc15f20..31af87670d59 100644
--- a/vcl/win/source/gdi/salgdi.cxx
+++ b/vcl/win/source/gdi/salgdi.cxx
@@ -809,7 +809,7 @@ bool WinSalGraphics::setClipRegion( const Region& i_rClip )
if(bUsePolygon)
{
- // #i122149# check the comment above to know that this may lead to potentioal repaint
+ // #i122149# check the comment above to know that this may lead to potential repaint
// problems. It may be solved (if needed) by scaling the polygon by one in X
// and Y. Currently the workaround to only use it if really unavoidable will
// solve most cases. When someone is really using polygon-based Regions he