Skip to main content

Report this content

We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.

Note that misuse of the reporting tool will not be tolerated.

Item being reported:

A forum post by TAPgiles

How are you progressing to a different screen? Can you not reverse that somehow?

If I were making a menu, I would use selectors for most things. The selector has multiple channels, and only one of them is "active" at a time and sends a signal. You can set which channel is active in a number of ways.

So for a particular list of items, I'd have the "selected" state of each menu item activated by a keyframe. I'd then wire each of those, in the correct order, to different selector channels. Then when I press up/down I'd trigger the selector's "previous"/"next" inputs (they wrap around the ends, by the way).

And to dictate which which menu is shown, I'd have a different selector that remembers which is being shown. Each channel would power a different chip that has that menu's items and selector in it. And to change which menu is being shown, I can send a signal *into* a channel to make it the active channel, and so power a different menu chip.

Though you may be doing it differently, which is fair enough. If I knew more about your existing setup I could give more specific advice?

Oh dear! Your browser is either unsupported or there has been a problem loading the page.