Jan
Jan
So for each Pin you add the klippain reference naming? could you give me an practical example for a pin in the png? In my current mindmap, it looks like...
aaaah, i saw these texts, but i wasn't sure if that was meant. so it is visualizing the alias in the "read only" cfgs, correct?
since we already went for detailed matching on the manufacturers pinout naming, the autogeneration is realistic for the current quality of the templates.
If someone can give me a hint, where to start, i can put some time into it. It helps me for another business project I am working on
Please make sure that the new variables have a meaningful default value in the macros you changed. Klippain Updaters do not get new variables in the variables.cfg integrated. Current state...
could you put this please in a draft state? Or can it be already integrated?
A pull request is not required to use/test a branch
Instead of checking for mmu.enabled would it be possible via rename existing to set klippain mmu enabled to false/true if the related function in MMU is used?
i changed the base to develop, hopefully to prevent the issues of last time
is it ready for review?