On Mon, 30 Dec 2002 18:02:54 -0500
"Norman Vine" <[EMAIL PROTECTED]> wrote:
It appears to me that you are *real close* to reinventing
the 'rule based' progamming paradigm.
There should be some 'CLIPS' experts running around the same
'hangars' that you frequent that might have some *good* inpu
Jon S Berndt writes:
< >
>
> VALUE="{property|value}">
> {property} {conditional} {property|value}
> ...
>
> VALUE="{property|value}">
> {property} {conditional} {property|value}
> ...
>
>...
>
>
> This is a request for developer community comment :-)
>
Arnt Karlsen writes:
> ..I propose (n-1) boolean bit settings for a n position
> rotary switch, translating Davids transponder example
> to 000 for OFF, 100 for SBY, 110 for ON and 111 for ALT.
That would be fine if there existed only one type of input for each
possible function, but the
On Mon, 30 Dec 2002 21:23:35 +0100
Arnt Karlsen <[EMAIL PROTECTED]> wrote:
..I propose (n-1) boolean bit settings for a n position
rotary switch, translating Davids transponder example
to 000 for OFF, 100 for SBY, 110 for ON and 111 for ALT.
Well, there is something to be said for bitfields
On Mon, 30 Dec 2002 12:52:13 -0600,
"Jon S Berndt" <[EMAIL PROTECTED]> wrote in message
<[EMAIL PROTECTED]>:
> On Mon, 30 Dec 2002 13:23:53 -0500
> David Megginson <[EMAIL PROTECTED]> wrote:
>
> >Jon S Berndt writes:
> >
> > > How are switches usually handled in the property system?
>
> >W
Jon S Berndt writes:
> Since the idea is to generalize this, I need to know only
> if a switch has "completed the circuit" (true), or not
> (false). Or, in the case of a situation where the specific
> aircraft in question has an autopilot rotary switch and
> can select (for example) OFF,
On Mon, 30 Dec 2002 13:23:53 -0500
David Megginson <[EMAIL PROTECTED]> wrote:
Jon S Berndt writes:
> How are switches usually handled in the property system?
When possible, it's nice to abstract the input more. For example,
lets say that you have a transponder with a rotary switch labelled
Jon S Berndt writes:
> How are switches usually handled in the property system?
> Is there state defined by 0/1, or true/false? In the case
> of rotary switches, I suppose those must be defined in a
> 0...n manner, no?
When possible, it's nice to abstract the input more. For example,
lets