cesars, thank you for your input.
I am new to XOD and just experimenting with it trying to put together simple circuits to see if I get expected results. I find that generally I DO NOT get expected results. Though I am not a professional programmer, I have programmed in many of the higher level languages (Visual Basic, Ruby, Python, some C++ and a little Assembler), and I have experimented with hardware circuits quite a bit as a hobby (to the point of building a functioning z-80 based micro-computer). I would like to use a “block based” or “visual” programming language to get away from the tedium of programming. But, I’m finding that the visual languages are either quite limited in capabilities or not especially intuitive.
I am putting XOD in the latter category. It seems quite powerful BUT I think it is a little misleading in the user interface because processes are constructed AS IF they were sequential, when, in fact, they apparently all occur simultaneously (in parallel). This is highlighted by your comment that you cannot “[use] D13 for two nodes simultaneously”. Of course, they do not APPEAR to be used simultaneously in the main patch. So far as the appearance of the main patch is concerned, it all LOOKS very sequential. But, apparently it is not. My intent was that each node be called sequentially, not in parallel. But sequential execution seems far more difficult than it should be.
I’ve experimented with Node Red before and it does appear to run sequentially, at least for the relatively simple projects that I made with it.
I wonder why XOD is designed so that a simple patch like mine does not work, but the rather complex “custom if-else” does - all because I cannot sequentially manipulate the same device from a sequence of nodes in my program. I am sure there are important design considerations that led to that, but I don’t know what those would be.
As you can tell, I’m not finding XOD particularly intuitive and am having a bit of a struggle with it.
please excuse my rant …