IrDA Framework
ContentsIndexHome
PreviousUpNext
Constants

The following table lists constants in this documentation.

Name 
Description 
The base error code for the WCL system/common errors.  
A connection is active.  
The base eror code for all connection errors.  
The connection has been closed.  
A connection is not active.  
The connection has been terminated by unknown reason.  
The connection has been terminated by user.  
Unable to create connection complete event object.  
Unable to create a communication thread initialization event.  
A server was not able to create or init client connection instance.  
Unable to create communication termination event object.  
A server was not able to find a specific client connection class.  
Unable to create communication thread.  
Unexpected error.  
One or more arguments passed into the method or function are invalid.  
Access denied.  
The component is already subscribed for the IrDA hardware change event.  
The requested attribute's class was not found.  
The requested attribute was not found.  
The base code for the IrDA errors.  
Connection already exsist.  
Connection has been rejected.  
Connection has been terminated by a user.  
Client disconnected by remote device.  
The Lazy Discovering is already running.  
The Lazy Discovering is not running.  
The IrDA subsystem or the associated service provider has failed.  
The specified handle type is not supported for IrDA communication.  
No more handles (descriptors) are available.  
A blocking call is in progress, or the service provider is still processing a callback function.  
An invalid argument was supplied.  
The descriptor is not a valid handle.  
The service provider returned an invalid or incomplete procedure table to the IrDA initialization.  
The service provider returned a version other than 2.2.  
A limit on the number of tasks supported by the IrDA implementation has been reached.  
No buffer space is available. The handle cannot be created.  
A successful IrDA subsystem initialization must occur before using this function.  
The underlying subsystem is not ready for communication.  
The component is not subscribed for the IrDA hardware change event.  
The IrDA is not supported. An infrared adapter and device driver is not installed on the local computer.  
The initialization parameter is not a valid pointer or One of the option value or the option length parameters is not a valid part of the user address space, or the option length parameter is too small.  
The specified protocol is not supported.  
An IrDA device or specific service was not found (address or service is invalid).  
The service provider failed to initialize. This error is returned if a layered service provider (LSP) or namespace provider was improperly installed or the provider fails to operate correctly.  
Timeout occured.  
Unable to create Lazy Discovering synchronization object.  
Unable to create Lazy Discovering thread.  
Unable to create socket event.  
Unable to create IrDA socket.  
Unable to get a read buffer size.  
Unable to get a write buffer size.  
Unable to select socket events.  
Unable to set a IrLMP communication mode.  
Unable to set a read buffer size.  
Unable to set a write buffer size.  
Unable to resolve a remote IrDA device address.  
Unexpected or unknown IrDA error.  
The option is unknown or unsupported by the indicated protocol family (IrDA).  
The version of IrDA subsystem support requested is not provided by this particular IrDA implementation.  
This connection mode can not be used for IrDA server.  
The specified protocol is the wrong type for this handle.  
The base error code for the message broadcaster.  
The message broadcaster can not initialize the hardware monitoring thread.  
The message broadcaster can not start the hardware monitoring thread.  
The message broadcaster was not created.  
A message receiver has already been subscribed.  
A message receiver has not been subscribed.  
There is the error with the references counter.  
The message broadcaster can not create the hardware monitoring object.  
The message broadcaster can not create a mutex synchronization object.  
The message broadcaster can not register for hardware changes notifications.  
The base error code for the message receiver.  
A message receiver has already been closed or not opened.  
A message receiver was not opened yet.  
A message receiver has already been opened.  
A thread synchronization object has not been created.  
A message receiver can not create a thread synchronization object.  
A message receiver can not register for threads synchronization.  
A message receiver can not synchronize threads and notify a "main" thread about new received message.  
Out of system memory.  
Operation completed with success.  
Thread user initialization failed.  
Unable to register thread message.  
The thread is not running.  
The thread is already running.  
Unable to post signal to the thread.  
Unable to create thread window.  
Unable to create thread.  
Unable to create thread initialization event.  
The base WinRT subsystem error code.  
WinRT initialization failed.  
Unable to active instance of the required class.  
Unable to create interface of the required class.  
Unable to create synchronization mutex for WinRT control.  
Unable to create string.  
unable to load WinRT core DLL.  
unable to load WinRT string DLL.  
 
 
 
 
Bluetooth Framework messages category.  
The connections and connection providers messages category.  
IrDA Framework messages category.  
Kinect Framework messages category.  
Serial Framework messages category.  
System messages category.  
USB Framework messages category.  
User defined message categories should start from this Category ID.  
WiFi Framework messages category.  
Wii remote Framework messages category.  
 
 
 
 
 
 
 
The Hardware Change message's ID.  
 
 
 
Copyright (c) 2006-2017. All rights reserved.