This article describes the implementation of a Windows Mobile desktop remote controller. With this application, you will be able to remotely control your Windows Mobile device by using the mouse and keyboard.
The code in this article builds on my previous article: A Remote Windows Mobile Screen Grabber. Instead of blocking RAPI calls, this application implements a streamed RAPI server that allows the desktop application to have a permanent connection to the device. Also, in this code, I have dropped the GAPI and DirectDraw screen grabbing techniques, and used a simpler GDI based screen grabbing technique. To improve communications performance, the code uses the ZLIB compression library on both ends.
Please refer to the CeRemoteClient directory on the distribution Zip file for the desktop project.
The bulk of the desktop code is on the CeRemoteClientView.h file. This is in fact a WTL 8.0 frame child window that implements all the desktop client features.
Device connection is performed via the public
Disconnect() methods. These are called by the menu and toolbar handlers in the frame window class implementation (MainFrm.h). When the desktop successfully connects to the device, a 200 millisecond timer is created to poll the device for the compressed screen bitmap.
The device screen is retrieved by the private
GetScreen() method. It first kills the timer, and sends a message to the device server requesting the current screen:
hr = Write(RCM_GETSCREEN);
The device server returns a message containing the same message code, the compressed size of the screen buffer, its expanded size, and the compressed byte stream. After reading the three first
DWORDs, the code makes sure there is enough room on both the compressed and expanded buffers, and then reads the compressed byte stream:
hr = m_pStream->Read(m_pZipBuf, cbZipBuf, &ulRead);
If all is well, the compressed buffer is decompressed and the resulting DIB is queried for the bitmap dimensions. If the dimensions are different than the last time, then it is very likely that the device screen was rotated, so the whole window is invalidated to erase any garbage:
zr = uncompress(m_pScrBuf, &nDestLen, m_pZipBuf, cbZipBuf);
if(zr == Z_OK)
DIBINFO* pDibInfo = (DIBINFO*)m_pScrBuf;
BYTE* pBmpData = (BYTE*)(m_pScrBuf + sizeof(DIBINFO));
BOOL bErase = FALSE;
if(m_xDevScr != pDibInfo->bmiHeader.biWidth ||
m_yDevScr != pDibInfo->bmiHeader.biHeight)
m_xDevScr = pDibInfo->bmiHeader.biWidth;
m_yDevScr = pDibInfo->bmiHeader.biHeight;
bErase = TRUE;
After forcing the window to update, the timer is restarted so we can get the next screen.
Sending keyboard and mouse input to the device is pretty simple: handle the corresponding window messages, convert their data content to
INPUT structures, and send them to the server for processing. Here's the
LRESULT OnKeyDown(TCHAR vk, UINT cRepeat, UINT flags)
input.type = INPUT_KEYBOARD;
input.ki.wVk = MapKey(vk);
input.ki.wScan = 0;
input.ki.dwFlags = 0;
input.ki.time = 0;
input.ki.dwExtraInfo = 0;
hr = Write(RCM_SETINPUT);
hr = Write(&input, sizeof(input));
MapKey() function performs basic key mappings between the desktop and the device keyboards. Use the F1 key for the left function button, and F2 for the right. The F3 and F4 keys naturally map to the phone keys.
Sending mouse actions is similar:
LRESULT OnLButtonDown(UINT Flags, CPoint pt)
m_bLeftBtn = true;
input.type = INPUT_MOUSE;
input.mi.dwFlags = MOUSEEVENTF_ABSOLUTE |
input.mi.dx = pt.x * 65536 / m_xDevScr;
input.mi.dy = pt.y * 65536 / m_yDevScr;
input.mi.mouseData = 0;
input.mi.time = 0;
input.mi.dwExtraInfo = 0;
hr = Write(RCM_SETINPUT);
hr = Write(&input, sizeof(input));
hr = GetScreen();
Note how the mouse screen coordinates are normalized for the device screen. This is a requirement of the
SendInput API used on the device server.
Now that I mentioned it, let's take a closer look at the device server code.
Please refer to the CeRemSrv directory on the distribution Zip file for the device project.
The bulk of the device code is implemented in the
CRemoteControl class. All messages sent by the desktop client are processed and dispatched on the executive loop implemented in the
The device screen is captured by the
SendScreen method which has a very similar structure to its desktop counterpart. Note how the device screen is captured so easily:
hDC = GetWindowDC(NULL);
After getting the HDC of the device screen, you can very easily copy it into a bitmap and serialize it to the desktop. There's no need for fancy GAPI or DirectDraw techniques like I used before.
After getting the device screen copied into a DIB, the whole thing is compressed and sent back to the desktop client:
memcpy(m_pScrBuf + i, m_dib.GetBitmapInfo(), sizeof(DIBINFO));
i += sizeof(DIBINFO);
memcpy(m_pScrBuf + i, m_dib.GetDIBits(), m_dib.GetImageSize());
i += m_dib.GetImageSize();
ULONG len = m_cbZipBuf;
int zr = compress(m_pZipBuf, &len, m_pScrBuf, cbNew);
if(zr != Z_OK)
len = 0;
hr = m_pStream->Write(&dwMsg, sizeof(DWORD), &ulWritten);
hr = m_pStream->Write(&len, sizeof(ULONG), &ulWritten);
hr = m_pStream->Write(&cbNew, sizeof(DWORD), &ulWritten);
hr = m_pStream->Write(m_pZipBuf, len, &ulWritten);
Handling input from the desktop is even simpler:
hr = m_pStream->Read(&input, sizeof(input), &dwRead);
if(dwRead != sizeof(input))
SendInput(1, &input, sizeof(input));
A very simple implementation indeed.
Points of interest
There are two interesting things you may like to know: how I simulated the double-click mouse event, and why this code will not work out of the box on WM5 and WM6 devices.
Double-clicks had to be simulated by sending four messages to the device. This happens because the desktop window manager will merge the four mouse events (down - up - down - up) into a single message -
WM_LBUTTONDBLCLK. If you look at my code, you will see how this was undone...
On WM5 and WM6 devices, you may have to enable RAPI connectivity in order for the device server DLL to respond to the client. I once wrote a simple device tool to help you with this nasty chore. You can get it here. Copy the EXE to the device and execute it.
- 2008-03-28 - Corrected flickering.
- 2008-03-17 - First release.
I work on R&D for Frotcom International, a company that develops web-based fleet management solutions.