<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4934.1600" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I've seen a lot of rotary encoder stuff in the
group, and until recently, I didn't understand what the fuss was all
about. With recent dialogue, I do - as far as what key combo is sent
depending on which way the knob was turned.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>This was something I always intended to take care
of with some sort of simple rotary switch and my EPIC. Say you have a
rotary with 10 contacts. That's 10 separate connections to the EPIC, and
in the EPIC program, all one would need to do is set up some fairly
straightforward logic to analyze where the rotary is at. If the program
simply stored the value associated with the current position of the knob, and
when a different contact of the 10 was detected, it would be compared to the
previously stored value, which would determine which way the knob was being
turned. This would give EPIC enought data to send whatever the appropriate
key combination was for increment or decrement.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Is there a flaw in this thinking?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Steve W.</FONT></DIV></BODY></HTML>