Now let's take a short look at the engine's core.

The hardware section of uICE is based on a driver layer, or probably better: a device plugin layer. With an easy to use but still versatile interface, developers can quickly extend uICE with support for any kind of receiver hardware.

Since device plugins are standard Windows dynamic link libraries, you can decide yourself whether your plugin can remain in the more convenient user mode or switching into kernel mode is required for your specific kind of hardware. uICE has a built-in decoding engine, so in most cases you don't have to bother with decoding sampled signals.

With its TCP/IP server, uICE offers a simple way for developers of other Windows applications to be remote-ready without accessing any hardware.
Client applications can receive user-readable, ready-to-use remote control commands, so you won't have to suffer from the pain of decoding strange remote control signal formats and can concentrate your efforts on developing a great application with an even greater experience for your users.

  Ease of use

Copyright © 1999-2003 MediaTexX