Tutorial talk:Combinator tutorial: Difference between revisions
Jump to navigation
Jump to search
SafwatHalaby (talk | contribs) |
SafwatHalaby (talk | contribs) |
||
| Line 9: | Line 9: | ||
:Thank you for this, designs are appreciated here. It's good that you remain objective about their advantages and disadvantages. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - <span style="color:#FF0000">Admin</span> 11:57, 13 May 2018 (UTC) | :Thank you for this, designs are appreciated here. It's good that you remain objective about their advantages and disadvantages. -- [[User:Bilka|Bilka]] ([[User talk:Bilka|talk]]) - <span style="color:#FF0000">Admin</span> 11:57, 13 May 2018 (UTC) | ||
:: Thank you for your incredible work on the Wiki. I am always 100% objective. It's worth noting that in this particular scenario, the initial design is objectively flawed. Try connecting a simple clock (self-connected arithmetic combinator with + 1) into it and then disconnecting it suddenly, its memory will flicker between the last two values. More generally, if the current input is only given for 1 tick, then it flickers between the current and the previous input. I do not want to remove it without the approval of the original poster. Here is a demo of the flicker. This device on the left sends a 1-tick pulse of 1. The lamp turns on if the output signal is 1. Here is a demo: | |||
https://streamable.com/a9buf | |||
== Binary gates redundant? == | == Binary gates redundant? == | ||
Revision as of 13:46, 13 May 2018
Memory cells
I am aiming to update the "memory cells" section.
- The "advanced cell" does not handle 1-tick bursts properly. (I updated the article and wrote about that)
- There should be more versions of the memory cell, including versions that can handle negative input.
I may post some of my designs here once I finish polishing them. -- SafwatHalaby (talk) 09:46, 13 May 2018 (UTC)
- Thank you for this, designs are appreciated here. It's good that you remain objective about their advantages and disadvantages. -- Bilka (talk) - Admin 11:57, 13 May 2018 (UTC)
- Thank you for your incredible work on the Wiki. I am always 100% objective. It's worth noting that in this particular scenario, the initial design is objectively flawed. Try connecting a simple clock (self-connected arithmetic combinator with + 1) into it and then disconnecting it suddenly, its memory will flicker between the last two values. More generally, if the current input is only given for 1 tick, then it flickers between the current and the previous input. I do not want to remove it without the approval of the original poster. Here is a demo of the flicker. This device on the left sends a 1-tick pulse of 1. The lamp turns on if the output signal is 1. Here is a demo:
Binary gates redundant?
The binary gates do not seem to have much function, because As of 0.16, arithmetic combinators have built-in binary logic support. -- SafwatHalaby (talk) 09:56, 13 May 2018 (UTC)
- I am not very experienced in combinators, but aren't the combinators OR, XOR and AND option bitwise instead of binary? User:My3DS changed the page to specify that just yesterday, so it seems important to me. -- Bilka (talk) - Admin 11:57, 13 May 2018 (UTC)
- I am not sure I understand the difference between "bitwise" and "binary" in the context of 1-bit inputs.
- The built-in OR, XOR, and AND produce exactly the same truth tables as the ones currently in the article for inputs of 1's and zeros, and are additionally capable of performing more than that for inputs greater than 1.
- -- SafwatHalaby (talk) 13:25, 13 May 2018 (UTC)