Hello Eduard,
I force pushed some fixes onto the unstable branch. The kmacro transcription is pleasantly working and an action duplication bug was identified and fixed. I am nearly comfortable pushing to master and tagging 0.6.0.
Here's the kmacro action commit
https://github.com/positron-solutions/dslide/commit/1123a4ecbe93d75816faa3ba9539d6aef4ed7ca3For anyone interested, I've been keeping the `dslide-action' class stable to keep custom actions stable. However, I need a capability to choose the next action correctly or to allow them to peek ahead and tell me which one should be next. Peeking may add complexity to actions but tracking their progress for them adds rigidity. If I decide to change actions, I'll make sure they are absurdly simple to write after the changes. I can always leave an optional method to support more complex ordering. Progress tracking and reading options off of elements is the bulk of all action creation, so doing it for them will make them brain dead simple. I think that's what we want.