Holographic Human-Computer Interface
Relationship between the H2CI and the CPU
The use of the Holographic Display Component (HDC) and Motion Detector (MD) to perform the input/output functions of the H2CI leaves the CPU free to perform typical CPU application functions without any additional processing burden from the H2CI (Fig. 2).
The MD would constantly scan for a command object within a prescribed threshold distance (Passive Tracking) from the displayed image (interactive 3D holograms, digital holography, holovideo, free space optics) or command point (Command Points). The threshold distance is essentially the size of a sphere between the location of the command object and the displayed image (Passive Tracking). This distance would be user-specified – similar to selecting cursor movement and style, screen taps, or gesture – to reflect the user's required sensitivity to movements of the command object. Options would include having the distance automatically adjusted based on the size of the displayed images or the distance between them.
The user would also specify a threshold time interval to permit the MD to detect the type of contact made by the command object – inadvertent, single, or multiple. Multiple contacts could be used with all objects, including command points, as appropriate.
When the command object performs a valid contact code (sequence of moves ) within the threshold distance and time, commands and actions for displayed objects are selected. The time and distance thresholds would assist the tracking algorithms in distinguishing real contacts of the command object from aberrant fluctuations.
The above functions would enable the H2CI's natural interaction between the application and the user. Specialized processors, memory, and storage components would be used in the HDC and MDC as appropriate for performance and cost.
|