Fooling around with Rulesets

This Article

This article describes some weird things I have found you can do with CT at the moment. Consider this an example of crazy things to do with rulesets?

This article focuses more on the code side of CT, and builds off of this article.

Number 1

Because of the way pynput works, in order to change the text you type, CT has to press backspace a couple times and then type in the new symbol. This means that the buffer that tracks your typing actually records what the symbol you just cycled to. This is the core logic behind the cycle_next function. Here's the shenanigans you can do because of this:

title: 2D LOOPS CHAOS
sections:
   base loop:
    - N: [E, ①, ②, ③, ④]

   individual loops:
    - n: [①, ⑴, ¹, ₁]
    - n: [②, ⑵, ², ₂]
    - n: [③, ⑶, ³, ₃]
    - n: [④, ⑷, ⁴, ₄]

It's a bit contrived, but It serves kind of as a dropdown menu, of sorts. I could only see this being useful in one circumstance where you can't afford to have 1, 2, 3, and 4 symbols used for this. Actually wait no, I can't see this being useful at all.

Maybe eventually I will make this display in the reference as a grid.

This program could easily hardly be extrapolated to n-dimensions if you so desire, but at that point, just get a macro board or give up.