Leider hab ich momentan nicht viel Zeit zum Basteln. Die neue Tool library is allerdings schwer in Arbeit (Russ, Dan, Brad, Gabriel, MJ, ...) und schaut fantastisch aus. Collision detection ist ziemlich weit oben auf sliptonic's Liste und die neuen Tools ist einer der Schritt in diese Richtung.

The page that details migration status is here: https://tracker.debian.org/pkg/pyside2 So it should be in 5 days. Thanks are due to looo too since I just noticed his post about the patches being used in the conda builds. Thank You! Thank You! Thank You! Today the changes showed up in Debian Testing...

kkremitzki wrote: ↑

Tue Mar 17, 2020 10:35 pm

Unfortunately things are in a bit of a broken state right now until the Debian Qt 5.14 transition is complete.

Do you know of an ETC for the transition for Debian Testing? Would be nice to build/use FC in/on my dev machine again.

You cannot overwrite the Op.... values, those are the ones as you correctly said, calculated by the operation. You can however overwrite on how (or if at all) those values are used by the operation. You want to look into the "SetupSheet", and if you're using those modifications all the time you prob...

Well done, love the outcome!
AFAIK there's only an integration for Machinekit

This is a considerable diversion from the current UX status quo and I was wondering where it comes from. The legend is displayed in the tooltip of the entry field, as it is for all other fields. Why we would want to add the legend for the "Output File" and not - for instance - for "Arguments", or th...

Those are actually the same thing, the library editor is where the tool table is defined. Not claiming that the naming convention is great, or even consistent - just providing some background. Personally I'm OK with either name.

Giulio Buccini wrote: ↑

Fri Feb 14, 2020 1:13 am

This is the best I can get when trying to mill the little platform (mill command: "profil based on edges"):

which version are you using? and can you upload your file?

Great page - are you looking for a review or for content?
If it's the latter, do you have an outline of what should go there?

I have a class in C++, let's call it A. A has a member function which returns objects of class B. 'thing is, B has a pointer to A. I know how to wrap A and all its members into a python class, APy - and I know how to wrap B into BPy. But what I can't figure out is how to add a reference from BPy to ...