Recognition of Eyes-free Handwriting Input for Pen and Touch Interfaces


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Recognition of Eyes-free Handwriting Input for Pen and Touch Interfaces
# 1  
Old 05-22-2008
Recognition of Eyes-free Handwriting Input for Pen and Touch Interfaces

HPL-2008-51 Recognition of Eyes-free Handwriting Input for Pen and Touch Interfaces - A., Bharath; Madhvanath, Sriganesh
Keyword(s): text input, pen and touch interfaces, handwriting recognition.
Abstract: Continuous handwriting input using the finger on small devices such as PDAs and mobile phones is difficult if not impossible. Also, handwriting input has always required significant attention from the user during the process of writing. In our previous work, we proposed the concept of 'eyes-free wri ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Solaris

Interfaces and Virtual-interfaces queries

Hi Al, In course of understanding networking in Solaris, I have these doubts on Interfaces. Please clarify me. I have done fair research in this site and others but could not be clarified. 1. In the "ifconfig -a" command, I see many interfaces and their configurations. But I see many... (1 Reply)
Discussion started by: satish51392111
1 Replies

2. UNIX for Dummies Questions & Answers

Touch all files and subdirectories (recursive touch)

I have a folder with many subdirectories and i need to set the modified date to today for everything in it. Please help, thanks! I tried something i found online, find . -print0 | xargs -r0 touch but I got the error: xargs: illegal option -- r (5 Replies)
Discussion started by: glev2005
5 Replies

3. Programming

Another set of eyes

Original code used fwrite instead of putc. What is expected is that the destination file will be written to. Instead I end up with a zero length file. I'm sure there is something simple I'm missing. tia. #include <stdio.h> #include <stdlib.h> #include <string.h> int main(int argc, char... (6 Replies)
Discussion started by: ramen_noodle
6 Replies

4. Shell Programming and Scripting

Need some help with this script -- extra eyes

I have two issues with this script. 1. I cannot seem to get my counters to count correctly. 2. My function to eject to CAP1 or CAP2 is hung in a loop and doens't exit back to the previous function. I would like to be able to select which cap to eject to . Each cap holds only 40 tapes, so when one... (15 Replies)
Discussion started by: gzs553
15 Replies
Login or Register to Ask a Question
TERASIC_MTL(4)						   BSD Kernel Interfaces Manual 					    TERASIC_MTL(4)

NAME
terasic_mtl -- driver for the Terasic/Cambridge Multi-Touch LCD device SYNOPSIS
device terasic_mtl In /boot/device.hints: hint.terasic_mtl.0.at="nexus0" hint.terasic_mtl.0.reg_maddr=0x70400000 hint.terasic_mtl.0.reg_msize=0x1000 hint.terasic_mtl.0.pixel_maddr=0x70000000 hint.terasic_mtl.0.pixel_msize=0x177000 hint.terasic_mtl.0.text_maddr=0x70177000 hint.terasic_mtl.0.text_msize=0x2000 DESCRIPTION
The terasic_mtl device driver provides support for the Terasic Multi-Touch LCD combined as controlled by a University of Cambridge's IP Core. Three device nodes are instantiated, representing various services supported by the device: terasic_regX Memory-mapped register interface, including touch screen input. terasic_pixelX Memory-mapped pixel-oriented frame buffer. terasic_textX Memory-mapped text-oriented frame buffer. terasic_mtl devices are also attached to the syscons(4) framework, which implements a VT-compatible terminal connected to the tty(4) frame- work. ttyvX device nodes may be added to ttys(5) in order to launch login(1) sessions at boot. Register, text, and pixel devices may be accessed using read(2) and write(2) system calls, and also memory mapped using mmap(2). SEE ALSO
login(1), ioctl(2), mmap(2), poll(2), read(2), write(2), syscons(4), tty(4), ttys(5) HISTORY
The terasic_mtl device driver first appeared in FreeBSD 10.0. AUTHORS
The terasic_mtl device driver and this manual page were developed by SRI International and the University of Cambridge Computer Laboratory under DARPA/AFRL contract (FA8750-10-C-0237) (``CTSRD''), as part of the DARPA CRASH research programme. This device driver was written by Robert N. M. Watson. BUGS
The syscons(4) attachment does not support the hardware cursor feature. A more structured interface to control registers using the ioctl(2) system call, would sometimes be preferable to memory mapping. For touch screen input, it would be highly desirable to offer a streaming interface whose events can be managed using poll(2) and related system calls, with the kernel performing polling rather than the userspace application. terasic_mtl supports only a nexus bus attachment, which is appropriate for system-on-chip busses such as Altera's Avalon bus. If the IP core is configured off of another bus type, then additional bus attachments will be required. BSD
August 18, 2012 BSD