@@ -1232,16 +1232,19 @@ Did that fix it?
12321232Huh. Nope.
12331233
12341234Sometimes you're really sure that you know what's wrong,
1235- it's just obvious,
1236- but you didn't know at all and you basically wasted your time.
1235+ it's just * so* obvious,
1236+ but you didn't know at all,
1237+ and you basically wasted your time with some dead end.
12371238This is frustrating, but it's okay.
1238- Happens to all of us.
1239- Oh well.
1239+ We all make mistakes.
12401240
1241+ In some web searches about this problem,
12411242I've heard that the mouse cursor sometimes is heuristic in Windows,
12421243and once Windows thinks that your app is behaving properly,
1243- it'll run the mouse cursor better for you.
1244- Maybe if we add more to our program it'll start working right.
1244+ it'll make the mouse cursor so the right thing for you.
1245+ I don't have any idea if this is true or not.
1246+ If it is true, then maybe once we add more to our program the mouse cursor will start working right.
1247+ Let's move on, we can come back to this later.
12451248
12461249## Painting The Window
12471250
@@ -1278,7 +1281,7 @@ unsafe_impl_default_zeroed!(RECT);
12781281This is all becoming routine by now, I hope.
12791282
12801283They want us to use [ BeginPaint] ( https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-beginpaint ) ,
1281- then FillRect] ( https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-fillrect ) on the whole canvas,
1284+ then [ FillRect] ( https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-fillrect ) on the whole canvas,
12821285then [ EndPaint] ( https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-endpaint ) .
12831286Sounds easy enough to do.
12841287
0 commit comments