Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chips should remember materials used when created #47

Open
Mordenkainen opened this issue Feb 6, 2012 · 3 comments
Open

Chips should remember materials used when created #47

Mordenkainen opened this issue Feb 6, 2012 · 3 comments

Comments

@Mordenkainen
Copy link
Collaborator

Chips should remember what materials were used when they were created.

Currently if you create a very compact circuit by using rcactivate to specify different IO materials to achieve density, then have to do an rcreset (or worse rcreset /all) things can get very ugly.

If the chips remembered what materials where specified when they were activated, then a re-activation of the chip should work with no special handling in most cases.

@Mordenkainen
Copy link
Collaborator Author

After looking at the other issues, this seems related to issue #37

@eisental
Copy link
Owner

eisental commented Feb 7, 2012

Yeah, that's exactly what I had planned for solving issue #37. Can you give an example, though, for when it helps using different io materials? I thought changing the chip block type would be enough in most cases.

@Mordenkainen
Copy link
Collaborator Author

Sure.

In this first picture, you can see a delay on the left built out of nether brick. It has to be moved out one block because it's layout would run it right up against the output blocks of some receivers. Even if the IO blocks were changed it would attempt to use the receiver output blocks if re-activated.

http://dl.dropbox.com/u/53001205/counter%201.png

In the second picture, we have the same circuit, with the "ideal" placement of the delay. It is using different chip material and IO blocks. This works fine, but on a reactivate it forgets that the IO blocks were changed and malfunctions.

http://dl.dropbox.com/u/53001205/counter%202.png

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants