Skip to content

Latest commit

 

History

History
73 lines (57 loc) · 2.55 KB

nf-ks-ksgetobjecttypefromfileobject.md

File metadata and controls

73 lines (57 loc) · 2.55 KB
UID title description old-location tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames f1_keywords topic_type api_type api_location api_name
NF:ks.KsGetObjectTypeFromFileObject
KsGetObjectTypeFromFileObject function (ks.h)
The KsGetObjectTypeFromFileObject function returns the AVStream object type that is associated with a given file object.
stream\ksgetobjecttypefromfileobject.htm
stream
04/12/2021
KsGetObjectTypeFromFileObject function
KsGetObjectTypeFromFileObject, KsGetObjectTypeFromFileObject function [Streaming Media Devices], avfunc_51a9a4d6-1481-45f9-918e-582907e8513c.xml, ks/KsGetObjectTypeFromFileObject, stream.ksgetobjecttypefromfileobject
ks.h
Ks.h
Universal
Available in Microsoft Windows XP and later operating systems and DirectX 8.0 and later DirectX versions.
Ks.lib
Any level
Windows
KsGetObjectTypeFromFileObject
ks/KsGetObjectTypeFromFileObject
APIRef
kbSyntax
LibDef
Ks.lib
Ks.dll
KsGetObjectTypeFromFileObject

KsGetObjectTypeFromFileObject function

-description

The KsGetObjectTypeFromFileObject function returns the AVStream object type that is associated with a given file object.

-parameters

-param FileObject [in]

A pointer to the FILE_OBJECT structure for which to determine the associated AVStream object type.

-returns

KsGetObjectTypeFromFileObject returns the object type of the AVStream object associated with FileObject as a KSOBJECTTYPE enumeration. This can be one of the following: KsObjectTypeDevice, KsObjectTypeFilterFactory, KsObjectTypeFilter, or KsObjectTypePin.

-remarks

The KsGetObjectTypeFromFileObject function does not check that the file object is associated with a KS object. If it is not, this may result in a memory access error. Driver developers should consider using structured exception handling to catch a possible exception.

-see-also

KsGetFilterFromFileObject

KsGetObjectFromFileObject

KsGetPinFromFileObject

KsPinGetConnectedPinFileObject