er, a "hobby".
I think you are underestimating , grossly , your success with this. There must be 1000s of consumers of this "hobby project" across the forums, and probably that accounts for 20% of the actual users who install it and never visit a forum. Wow, you really are humbling yourself mate.
I write documentation if not at least in the code, so I can remember the design time decisions, workflow, data modelling and interface considerations taken. But then again I tend to work alone and not part of a team because I'm the only developer in this business function. Maybe if I was part of a team, working on but one project, and working only on a small module, then I could remember aforementioned.
I have asked the devs, havent I, by coming on here ??? And believe me, god, I have looked at the enigma code and tried to work through the undocumented tangle of coupled modules and packages, but you have to remember that I am trying to figure out what is in the devs' heads aren't I, from no docs and little support.
I am grateful you take the time to post here, but perhaps as a dev, you could enlighten me as to what modules (.py) provide event driven models that which I can use to either time slice a function (pre-emptive interrupts) , or if enigma/python stack doesnt offer this, then some kind of function that I can call to allow engima to paint/update, or if that isnt available then a timer with callback that will invoke my callback every N seconds in which case my callback will then have to deal with restricting execution time to prevent the main loop blocking - incidentally, what is the time period after which the spinner and debug message is displayed "main loop taking longer than expected" or whatever it was??