Heres an initial port of the PSpline.pas to C,
(single C file, prints 2d curve to stdout).
https://gitlab.com/ideasman42/fred-curve/blob/HEAD/pspline.c
This is the n-dimensional variant, but for the test it only prints 2d values.
My main concern with this method of calculating splines is it
Hm.. I'm not sure it would be very useful. Seems like it would be a bit
of a trick to decide what operations are crash capable. For me at
least, Blender hardly ever crashes while rendering or baking (or at all
for that matter :D), whenever it *does* happen it seems like it's some
spontaneous
Ugh, never mind, floating point splines aren't any trouble :)
https://gitlab.com/ideasman42/fred-curve/blob/float_spline/pspline.c
On Sat, Dec 27, 2014 at 9:23 PM, Campbell Barton ideasma...@gmail.com wrote:
Heres an initial port of the PSpline.pas to C,
(single C file, prints 2d curve to
Yeah, naming the auto save files in an easy to recognize way will help.
rexford | google.com/+Nkansahrexford
On Dec 27, 2014 7:08 AM, gandalf3 zzyx...@gmail.com wrote:
I often end up searching through a small heap of auto-save files trying
to find the one for the file on which I was working.
IIRC this feature was committed in master not too long ago (just over a month or
so): https://developer.blender.org/rBba872f022cd40d3ff9f2314830dcac5204a6c506
I just checked with 2.73 and it works fine for me. Is that what you're looking
for?
-Jason
Nkansah Rexford nkansahrexf...@gmail.com
Regarding devs adding/removing trailing whitespace.
- https://developer.blender.org/rB0fc0cb351b5e838dce7a14e8fe68fb6f7125eab0
- https://developer.blender.org/rB5d8a207b67aee18cadec742246b9dc9c052bd344
- https://developer.blender.org/rBfd4720204399e16032574159699d5a26a250e6d5
-
While i agree such changes are real PITA the proposed statement in wiki is
too vague IMO.
Is indentation fix a minor or not? Is brace placement changes minor or not?
This is a bit unclear and needs more clear statement (since i know one guy
who does all sort of cleanup all over the code :)
Also,
Wow, that's great, thanks! :D
The devs are so fast they add features *before* they are requested ;)
On 12/27/14 11:59, Jason van Gumster wrote:
IIRC this feature was committed in master not too long ago (just over a month
or
so):
On Sun, Dec 28, 2014 at 7:37 AM, Sergey Sharybin sergey@gmail.com wrote:
While i agree such changes are real PITA the proposed statement in wiki is
too vague IMO.
Yep, this could be nailed down better. (I wanted to avoid writing a
lot of details but, seems being brief here isnt helpful!)
So for the best practice section i guess we should add:
- Avoid modifying whitespace (indentation, trailing whitespace) for code
your commit doesn't change
- Avoid having trailing whitespace in the new code
- Don't do minor cleanup to existing code (such as trailing whitespace
change) (note:
respect!
pio
Piotr Arłukowicz, PhD, BFCT
University of Gdańsk, Faculty of Mathematics, Physics and Informatics,
Dept. of AI,
Wit Stwosz 57, 80-952 Gdańsk, room 121, tel.: +48585232151,
https://inf.ug.edu.pl/~piotao
Polish Blender Course: http://polskikursblendera.pl/ [PL]
2014-12-27 11:39
11 matches
Mail list logo
