Skip to content

Commit cd999d5

Browse files
authored
Merge pull request #2914 from TylerMSFT/twhitney-githubissues
Better example and small acrolinx fixes
2 parents 08e4028 + ef449ca commit cd999d5

2 files changed

Lines changed: 14 additions & 14 deletions

File tree

docs/mfc/reference/cftpfilefind-class.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,15 @@ class CFtpFileFind : public CFileFind
2727

2828
|Name|Description|
2929
|----------|-----------------|
30-
|[CFtpFileFind::FindFile](#findfile)|Finds a file on a FTP server.|
30+
|[CFtpFileFind::FindFile](#findfile)|Finds a file on an FTP server.|
3131
|[CFtpFileFind::FindNextFile](#findnextfile)|Continues a file search from a previous call to [FindFile](#findfile).|
3232
|[CFtpFileFind::GetFileURL](#getfileurl)|Gets the URL, including path, of the found file.|
3333

3434
## Remarks
3535

3636
`CFtpFileFind` includes member functions that begin a search, locate a file, and return the URL or other descriptive information about the file.
3737

38-
Other MFC classes designed for Internet and local file searched include [CGopherFileFind](../../mfc/reference/cgopherfilefind-class.md) and [CFileFind](../../mfc/reference/cfilefind-class.md). Together with `CFtpFileFind`, these classes provide a seamless mechanism for the client to find specific files, regardless of the server protocol or file type (either a local machine or a remote server). Note that there is no MFC class for searching on HTTP servers because HTTP does not support the direct file manipulation required for searches.
38+
Other MFC classes designed for Internet and local file searched include [CGopherFileFind](../../mfc/reference/cgopherfilefind-class.md) and [CFileFind](../../mfc/reference/cfilefind-class.md). Together with `CFtpFileFind`, these classes provide a seamless mechanism for the client to find specific files, regardless of the server protocol or file type (either a local machine or a remote server). There's no MFC class for searching on HTTP servers because HTTP doesn't support the direct file manipulation required for searches.
3939

4040
For more information about how to use `CFtpFileFind` and the other WinInet classes, see the article [Internet Programming with WinInet](../../mfc/win32-internet-extensions-wininet.md).
4141

@@ -73,11 +73,11 @@ explicit CFtpFileFind(
7373
A pointer to a `CFtpConnection` object. You can obtain an FTP connection by calling [CInternetSession::GetFtpConnection](../../mfc/reference/cinternetsession-class.md#getftpconnection).
7474

7575
*dwContext*<br/>
76-
The context identifier for the `CFtpFileFind` object. See **Remarks** for more information about this parameter.
76+
The context identifier for the `CFtpFileFind` object. For more information, see the following **remarks**.
7777

7878
### Remarks
7979

80-
The default value for *dwContext* is sent by MFC to the `CFtpFileFind` object from the [CInternetSession](../../mfc/reference/cinternetsession-class.md) object that created the `CFtpFileFind` object. You can override the default to set the context identifier to a value of your choosing. The context identifier is returned to [CInternetSession::OnStatusCallback](../../mfc/reference/cinternetsession-class.md#onstatuscallback) to provide status on the object with which it is identified. See the article [Internet First Steps: WinInet](../../mfc/wininet-basics.md) for more information about the context identifier.
80+
The default value for *dwContext* is sent by MFC to the `CFtpFileFind` object from the [CInternetSession](../../mfc/reference/cinternetsession-class.md) object that created the `CFtpFileFind` object. You can override the default to set the context identifier to a value of your choosing. The context identifier is returned to [CInternetSession::OnStatusCallback](../../mfc/reference/cinternetsession-class.md#onstatuscallback) to provide status on the object with which it's identified. See the article [Internet First Steps: WinInet](../../mfc/wininet-basics.md) for more information about the context identifier.
8181

8282
### Example
8383

@@ -96,20 +96,20 @@ virtual BOOL FindFile(
9696
### Parameters
9797

9898
*pstrName*<br/>
99-
A pointer to a string containing the name of the file to find. If NULL, the call will perform a wildcard search (*).
99+
A pointer to a string containing the name of the file to find. If NULL, the call will do a wildcard search (*).
100100

101101
*dwFlags*<br/>
102102
The flags describing how to handle this session. These flags can be combined with the bitwise OR operator (&#124;) and are as follows:
103103

104-
- INTERNET_FLAG_RELOAD Get the data from the wire even if it is locally cached. This is the default flag.
104+
- `INTERNET_FLAG_RELOAD` Get the data from the wire even if it's locally cached. This is the default flag.
105105

106-
- INTERNET_FLAG_DONT_CACHE Do not cache the data, either locally or in any gateways.
106+
- `INTERNET_FLAG_DONT_CACHE` Don't cache the data, either locally or in any gateways.
107107

108-
- INTERNET_FLAG_RAW_DATA Override the default to return the raw data ( [WIN32_FIND_DATA](/windows/win32/api/minwinbase/ns-minwinbase-win32_find_dataw) structures for FTP).
108+
- `INTERNET_FLAG_RAW_DATA` Override the default to return the raw data ( [WIN32_FIND_DATA](/windows/win32/api/minwinbase/ns-minwinbase-win32_find_dataw) structures for FTP).
109109

110-
- INTERNET_FLAG_SECURE Secures transactions on the wire with Secure Sockets Layer or PCT. This flag is applicable to HTTP requests only.
110+
- `INTERNET_FLAG_SECURE` Secures transactions on the wire with Secure Sockets Layer or PCT. This flag applies to HTTP requests only.
111111

112-
- INTERNET_FLAG_EXISTING_CONNECT If possible, reuse the existing connections to the server for new `FindFile` requests instead of creating a new session for each request.
112+
- `INTERNET_FLAG_EXISTING_CONNECT` If possible, reuse the existing connections to the server for new `FindFile` requests instead of creating a new session for each request.
113113

114114
### Return Value
115115

@@ -159,7 +159,7 @@ The file and path of the Universal Resource Locator (URL).
159159

160160
### Remarks
161161

162-
`GetFileURL` is similar to the member function [CFileFind::GetFilePath](../../mfc/reference/cfilefind-class.md#getfilepath), except that in addition to providing the result in URL format, it doesn't include the filename. For example:`ftp://moose/dir`.
162+
`GetFileURL` is similar to the member function [CFileFind::GetFilePath](../../mfc/reference/cfilefind-class.md#getfilepath) except that it provides the result in URL format. As with `CFileFind::GetFilePath`, the result doesn't include the filename. For example, `file1.txt` located in `//moose/dir/file1.txt:` returns `ftp://moose/dir/`.
163163

164164
## See also
165165

docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -354,7 +354,7 @@ Next, you'll learn how to create the code for a Windows desktop application in V
354354
355355
One important message to handle is the [WM_PAINT](/windows/win32/gdi/wm-paint) message. The application receives the `WM_PAINT` message when part of its displayed window must be updated. The event can occur when a user moves a window in front of your window, then moves it away again. Your application doesn't know when these events occur. Only Windows knows, so it notifies your app with a `WM_PAINT` message. When the window is first displayed, all of it must be updated.
356356
357-
To handle a `WM_PAINT` message, first call [BeginPaint](/windows/win32/api/winuser/nf-winuser-beginpaint), then handle all the logic to layout the text, buttons, and other controls in the window, and then call [EndPaint](/windows/win32/api/winuser/nf-winuser-endpaint). For the application, the logic between the beginning call and the ending call displays the string "Hello, Windows desktop!" in the window. In the following code, the [TextOut](/windows/win32/api/wingdi/nf-wingdi-textoutw) function is used to display the string.
357+
To handle a `WM_PAINT` message, first call [BeginPaint](/windows/win32/api/winuser/nf-winuser-beginpaint), then handle all the logic to lay out the text, buttons, and other controls in the window, and then call [EndPaint](/windows/win32/api/winuser/nf-winuser-endpaint). For the application, the logic between the beginning call and the ending call displays the string "Hello, Windows desktop!" in the window. In the following code, the [TextOut](/windows/win32/api/wingdi/nf-wingdi-textoutw) function is used to display the string.
358358
359359
```cpp
360360
PAINTSTRUCT ps;
@@ -379,8 +379,8 @@ Next, you'll learn how to create the code for a Windows desktop application in V
379379
}
380380
```
381381

382-
`HDC` in the code is a handle to a device context, which is a data structure used to communicate with the graphics subsystem about the window. Calling `BeginPaint` and `EndPaint` tells the graphics subsystem that you are updating the invalidated region and that no more painting is required until it is invalidated again. Otherwise, you will keep getting WM_PAINT messages for that region.
383-
382+
`HDC` in the code is a handle to a device context, which is used to draw in the window's client area. Use the `BeginPaint` and `EndPaint` functions to prepare for and complete the drawing in the client area. `BeginPaint` returns a handle to the display device context used for drawing in the client area; `EndPaint` ends the paint request and releases the device context.
383+
384384
1. An application typically handles many other messages. For example, [WM_CREATE](/windows/win32/winmsg/wm-create) when a window is first created, and [WM_DESTROY](/windows/win32/winmsg/wm-destroy) when the window is closed. The following code shows a basic but complete `WndProc` function.
385385

386386
```cpp

0 commit comments

Comments
 (0)