|
IMoniker::ParseDisplayName
Reads as many characters of the specified display name as it understands and
builds a moniker corresponding to the portion read; this procedure is known as
"parsing" the display name.
HRESULT ParseDisplayName(
IBindCtx *pbc,
| //Bind context to be used
| IMoniker *pmkToLeft,
| //Moniker to the left in the composite
| LPOLESTR pszDisplayName,
| //Display name
| ULONG *pchEaten,
| //Receives number of characters consumed
| IMoniker **ppmkOut
| //Receives moniker built from display name
| );
|
|
Parameters
pbc
[in] Points to the bind context to be used in this binding operation. The bind
context caches objects bound during the binding process, contains parameters
that apply to all operations using the bind context, and provides the means by
which the moniker implementation should retrieve information about its
environment. For more information, see IBindCtx.
pmkToLeft
[in] Points to the moniker that has been built out of the display name up to
this point.
pszDisplayName
[in] Points to a zero-terminated string containing the remaining display name
to be parsed. For Win32 applications, the LPOLESTR type indicates a wide character string (two bytes per character); otherwise,
the string has one byte per character.
pchEaten
[out] Receives the number of characters in pszDisplayName that were consumed in this step.
ppmkOut
[out] Receives a pointer to the moniker that was built from pszDisplayName. If an error occurs, the implementation sets *ppmkOut to NULL. If *ppmkOut is non-NULL, the implementation must call IUnknown::AddRef on the parameter; it is the caller's responsibility to call IUnknown::Release.
Return Values
S_OK
The parsing operation was completed successfully.
MK_E_SYNTAX
Indicates an error in the syntax of the input components (pmkToLeft, this moniker, and pszDisplayName). For example, a file moniker returns this error if pmkToLeft is non-NULL, and an item moniker returns it if pmkToLeft is NULL.
E_OUTOFMEMORY
Indicates insufficient memory.
E_UNEXPECTED
Indicates an unexpected error.
IMoniker::BindToObject errors
Parsing display names may cause binding. Thus, any error associated with this
function may be returned.
Comments
Notes to Callers
Moniker clients do not typically call IMoniker::ParseDisplayName directly. Instead, they call the MkParseDisplayName API function when they want to convert a display name into a moniker (for
example, in implementing the Links dialog box for a container application, or for
implementing a macro language that supports references to objects outside the
document). That API function first parses the initial portion of the display
name itself. It then calls IMoniker::ParseDisplayName on the moniker it has just created, passing the remainder of the display name
and getting a new moniker in return; this step is repeated until the entire
display name has been parsed.
Notes to Implementors
Your implementation may be able to perform this parsing by itself if your
moniker class is designed to designate only certain kinds of objects. Otherwise,
you must get an IParseDisplayName interface pointer for the object identified by the moniker-so-far (i.e., the
composition of pmkToLeft and this moniker) and then return the results of calling IParseDisplayName::ParseDisplayName.
There are different strategies for getting an IParseDisplayName pointer:
- You can try to get the object's CLSID (for example, by calling IPersist::GetClassID on the object), and then call the CoGetClassObject API function, requesting the IParseDisplayName interface on the class factory associated with that CLSID.
- You can try to bind to the object itself to get an IParseDisplayName pointer.
- You can try binding to the object identified by pmkToLeft to get an IOleItemContainer pointer, and then call IOleItemContainer::GetObject to get an IParseDisplayName pointer for the item.
Any objects that are bound should be registered with the bind context (see IBindCtx::RegisterObjectBound) to ensure that they remain running for the duration of the parsing operation.
See Also
IParseDisplayName, MkParseDisplayName
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers Software for Delphi and C++ Builder developers Software for Visual Basic 6 developers Delphi Tips&Tricks MegaDetailed.NET More Online Helps Win32 Programmer's Reference Win32 Multimedia Programmer's Reference OLE Programmer's Reference Microsoft Windows Pen API Programmer's Reference Microsoft Windows Sockets 2 Reference Microsoft Windows Telephony API (TAPI) Programmer's Reference Unix Manual Pages
|