11 hours ago · Tech · 0 comments

Still working on Lever-Spike connection. I was right not to panic yesterday, the snag wasn’t a snag. Hello, loves. I was concerned yesterday that the Animated item (in its role as Spikes) was going to be hearing its own messages. I had not realized that the caller ID feature would handle that. The Lever will publish state with the caller ID ‘spikes’, and the Spikes will subscribe to that. The Spikes will publish state using caller ID ‘view’, and we will not subscribe to that. So I was right not to panic. Go, me! We are engaged in making the spikes behave differently depending on the state of the lever. Sometimes they cycle, sometimes they stop in the up position, sometimes down. We will also need them to do some damage to poor Innocent Intrepid Adventurer Dot. We’ll begin by making the spikes just stop cycling on hearing any non-zero state from the Lever. Let’s see what the class looks like now: class Animated(Content): @classmethod def spikes(cls, name): resource1 =…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.