Expression Gate 2

[chinoto]

Quick! Flamewar about implementing functions to prevent that thread from being longer than this one. (I don't really care about the functions, its just a neat idea to me)

[Lancelot]

It's a useful one. The things it would allow people to do would be incredible, and leave the code much cleaner. I'm working on a fin aircraft right now and trying to work out the autopilot. I could say, have a function that makes the plane go somewhere, another that makes it circle that location, take off, land, allow manual control etc. Then you also need a function to get and display telemetry. Instead right now functions need to be cheaply mimicked.

[Drunkie]

Instead right now functions need to be cheaply mimicked.

The dev's are aware about that. Functions have been suggested like thousands of times.

[nachosdan]

I was wondering, how the code for an edge-triggered gate would look. I have been working with expression gates for about 10 minutes, but I've worked with HTML, PHP and javascript before.
Could it look something like this?

if ((A==1 | B==1) & C!=1) {C=1}
else {C=0}

if (C==1) {X=1}

[Divran]

Not 100% sure what "edge" triggered actually does, but if I'm right, it's:

@inputs Toggle OnValue OffValue
@outputs Out
if (~Toggle & !Toggle) {
    Out = (Out == OnValue ? OffValue : OnValue)
}

[Colonel Thirty Two]

It means it triggers when an input is changed. In digital electronics the waveform goes from 0 instantly to 1, hence creating an "edge."

[Divran]

It means it triggers when an input is changed. In digital electronics the waveform goes from 0 instantly to 1, hence creating an "edge."

So say you have a button. Should it toggle when you first touch the button, or should it do nothing while you hold your finger down on it, and only react when you let go of the button? I have the second of the two in the above code. To change it into the first, simply remove the "!" from in front of the second "Toggle".

[nachosdan]

Thank you. I messed my question a bit up, I think. I'm looking for a code, so I can have 2 buttons on each side of a door and then another button inside to lock the door.

[ufoslava]

So say you have a button. Should it toggle when you first touch the button, or should it do nothing while you hold your finger down on it, and only react when you let go of the button? I have the second of the two in the above code. To change it into the first, simply remove the "!" from in front of the second "Toggle".

@trigger-directive The trigger directive can selectively enable or disable inputs from triggering executions. Possible values are all/none, but also a list of inputs.
@trigger all # old behaviour, inputs always trigger executions
@trigger none # will never trigger from inputs, only timers, etc
@trigger Time Button # will only trigger if Time or Button has changed

So there you have it... make your expression run every time value is changed.

Also, toggle button changes the value the moment you press it, no matter if you hold it or not.
Non-toggle button changes the value back the moment you release it.

[Colonel Thirty Two]

Nice bump. -_-