fixed bug in mouse handling

[wxWidgets.git] / docs / latex / wx / tbitmap.tex

diff --git a/docs/latex/wx/tbitmap.tex b/docs/latex/wx/tbitmap.tex
index 7dd47bd461a0080108c23afeffc4d2f806bea37f..8b45fe14787c8f8313054921a54a31070573e131 100644 (file)
--- a/docs/latex/wx/tbitmap.tex
+++ b/docs/latex/wx/tbitmap.tex
@@ -69,7 +69,7 @@ wxBitmap bmp(wxBITMAP(bmpname));
 
 You should always use wxICON and wxBITMAP macros because they work for any
 platform (unlike the code above which doesn't deal with wxMac, wxBe, ...) and
 
 You should always use wxICON and wxBITMAP macros because they work for any
 platform (unlike the code above which doesn't deal with wxMac, wxBe, ...) and

-are more short and clear than versions with {\tt #ifdef}s.
+are more short and clear than versions with {\tt \#ifdef}s.

 
 \subsection{Supported bitmap file formats}\label{supportedbitmapformats}
 
 
 \subsection{Supported bitmap file formats}\label{supportedbitmapformats}
 


@@ -80,7 +80,7 @@ it to wxBitmap form. Note that using wxImage is the preferred way to
 load images in wxWindows, with the exception of resources (XPM-files or
 native Windows resources). Writing an image format handler for wxImage
 is also far easier than writing one for wxBitmap, because wxImage has
 load images in wxWindows, with the exception of resources (XPM-files or
 native Windows resources). Writing an image format handler for wxImage
 is also far easier than writing one for wxBitmap, because wxImage has

-exactly one format on all platforms wheras wxBitmap can store pixel data
+exactly one format on all platforms whereas wxBitmap can store pixel data

 very differently, depending on colour depths and platform.
 
 \wxheading{wxBitmap}
 very differently, depending on colour depths and platform.
 
 \wxheading{wxBitmap}