Ok, so easier than I thought. Hopefully. for (var i:int = 0; i < kid.length;i++) { kid[i].engine(connectList[i]); } changed to: for (var i:String in kid) { kid[i].engine(connectList[i]); } This iterates through the indexes of kid which are created using the output port of the originating modules. so they might look like this: kid[0]==led1 kid[9]==led2 and […]
Continue readingAuthor: sambaker
Reverse Engineering
This is the most recent build. It has some subtle differences with the previous version, most notably, if you light the led by entering a number higher than 0 in the integer module, then press and release the button also connected to the led, it will go off. Also, you can change the contents of […]
Continue readingRoadblock Ahead
Few more changes brings me closer to actual NeatTools behavior, and data flow. When evoking a module’s engine() method, the module is now passed the incoming port number. Every module has three arrays:mom, kid, and connectionList. When a connection is created the arrays are updated. Both kid and mom are arrays of modules, connectionList is […]
Continue readingEvent Broadcast Model Saved My Marriage
Not really, but I’ve been reading up on how it’s used in NeatTools, both from EJ’s Thesis, and from an analysis done by Rob Salgado. I’ve tried to replicate it to the best of my abilities within my code, and while it’s still a work in progress, it’s already done two things for my program. […]
Continue readingThe Wires are the Thing
After dealing with two new module types and incorporating them into the mix, I’m starting to think I need to rethink my module interaction model. Right now modules communicate directly with those modules they have connections with. To make the Integer module talk to the Add module, because they each handle data differently, I had […]
Continue reading