Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
You want an input (A) that might be a pulse, stored in the latch & output continuously. That bit is clear, & quite simple to setup.
But what should it do when it recieves a new (A) signal? Should it overwrite the one in the latch if it is less / greater than the stored value? Or always overwrite if it is a different value?
Same question about the second input (B) ~ should that one always overwrite the value stored in the latch, or only if it is different / less / greater?
What about if there is a signal on both (A) and (B) inputs at the same tick ~ should the latch combine them together, or store the highest / lowest input only, or always prefer (A) over (B) input?
Will the inputs be positive integers, or does it need to support storing negative values also?
If you can provide some more details, a solution should be entirely possible to build.
That's effective enough for what I want, thank you.
I do wonder how you'd adapt it so I goes straight through when there's input, but I can play and discover that myself.
Much appreciated.