Expecting to copy/paste mathematical equations or formulas from a wikipedia page or a DAFx conference paper and get a working implementation, is unrealistic.
Window functions are often implemented with look-up tables, not by direct function evaluation. In DSP often formulas
are approximated when implementing them. Or some formula's don't even describe an implementation.
Yeah I also thought it might be expecting a bit too much. BUt if possible it would be great 
I do know that it probably had to be adjusted a bit and not DIRECTLY copy pasting. BUt you get the idea I am sure.
Thank you fo the answer
Apologies if I keep mentioning it, but it's the node-based editor I have most experience oh..
Quartz Composer has a mathematical function object. It's pretty useful. On the other hand, it doesn't implement variable typing, so maybe it wouldn't translate well to the Axoloti environment.
a|x
What about a short-cut to toggle the Live mode on and off?
(Maybe there is such short-cut and I missed it?).
heres a little one, but it would make patching much faster; on osx, when i pull up the object window i need to select an object from the list and THEN im able to arrow up and down. it would be great if i could type an object name and then arrow down to the one i want.
in other words its mouse, type, mouse, type. instead of mouse, type, type, type. .
like i said, just a small annoyance, but it would make patching alot smoother and faster for me 
Press tab to move focus from the object name field to the list,
shift-tab to move focus back.
The ability to convert a subpatch into a patcher object version of the subpatch.
This would be very handy if you load a subpatch from the browser in Axoloti and then still want to edit the subpatch from patch to patch. The you could just push the "convert to patcher object" button and Axoloti converts the subpatch to a patcher object, which can then be edited, without worrying about messing up other songs or patches.
The Object Browser is the single item most in need of some attention in the current Patcher, I'd say.
It at the Least needs to be resizable, but having it constantly visible, or even docked to one side of the Patch window, would in my view be a great improvement.
a|x
Also, I don't think the width of an object should be determined purely by the length of the title string.
I don't think we need any part of the file path of the object in the title- just the object name should be sufficient.
The path could be displayed in a tooltip when rolling over the title.
Personally, I think it would look much neater if the widths of all objects conformed to the same grid used to snap their positions.
a|x
Yes just tried it. Nice. But it is not possible to edit the patch afterwards, besides form the code editor. Would be awesome if it was just another regular patcher object that you can edit as others.
Anyway, happy to finally be onboard the "new school" Axoloti
Object layout, adding the ability to customize the position of different controls within the frame is certainly something I want to improve, and yes object type name or instance name should not affect size.
Hmmm but it is sometimes used to differentiate: osc/sine versus lfo/sine versus math/sine
I did not like the max/pd style ~ suffix, the tilde character is hard to reach on many keyboard layouts.
But that is already the case, no?
Fair points. I don't see the problem with having a truncated name in the titlebar, and a more specific path in a tooltip that appears when you roll over the titlebar.
a|x
there is an 'ideal' that you can reproduce a patch from a screenshot...so that might be slightly hindered by using tooltips. though, id say most of the time, the end part of the name is likely to be enough.
I think this ideal does have merits... here on the forum, when explaining things, you can simply post a screenshot, or even part of a screen, to give the idea of whats happening in the patch.
... but as i said, perhaps the end part is enough for this purpose.