Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Frostebite
@frostebite
@AQuentin2033 Hey, thanks for that answer. I'm not looking for anything other than the ability to test a ray or similar, against a triangle in 3d and get if there is an intersection and the coordinate of the intersection.
Adam Miller
@millera023
Is there anywhere for me to get an updated Nuget package newer than 0.4?
Johan Larsson
@JohanLarsson
unfortunately no
we really need to pack and publish
I don't know how the scipts work
mathnet/mathnet-spatial#158
the situation is not good
plenty of work has gone in unreleased
Adam Miller
@millera023
Could anyone direct me to what Point2D's ToPoint3D() method is being replaced with? I see the comment saying to "Use projections instead"...but I'm honestly not for sure what that means.
Johan Larsson
@JohanLarsson
I'd just do new Point3D(p.X, p.Y, 0)
where do you see the comment? maybe we can make it clearer?
Adam Miller
@millera023
Line 341 in Point2D.cs
I'm new to using gitter...so I see some people can link things...I don't know If I can link that or not...haha
Johan Larsson
@JohanLarsson
https://github.com/mathnet/mathnet-spatial/blob/master/src/Spatial/Euclidean/Point2D.cs#L341
click on the line number on github and copy the url from the browser
nice ux
Adam Miller
@millera023
Oh, neat.
Johan Larsson
@JohanLarsson
youc an also select ranges etc
also, nice that you found gitter
chat is a nice complement to issues
Adam Miller
@millera023
For sure. It's great to have a forum to directly ask questions and discuss things around libraries.
Johan Larsson
@JohanLarsson
ok, that message does not make things very clear, was probably I who wrote it, we should write something better
question is what to write?
Adam Miller
@millera023
I'm especially unsure because your suggestion to my original question is to do what that method does :)
Johan Larsson
@JohanLarsson
reason for making the method obsolete is that it is in the category of useless helpers that don't make anything clearer
Adam Miller
@millera023
That makes sense, I guess the clarity issue may come from the word "projections" in the current comment. It's a bit ambiguous as to what is actually meant.
Also...someone on my team may end up packaging this project up (right now we are just building from source as we test some things out...)...If that happens would anyone here be interested on what he does?
Johan Larsson
@JohanLarsson
We should have some kind of readme with the steps
He can perhaps pr a readme or reply on #158?
there is also the documentation site etc.
not trying to make it sound like an impossible task btw :)
just that I don't know how to pack and publish it
Johan Larsson
@JohanLarsson
we wrote an analyzer with fixes for some of the breaking changes
for convenience when used from c#
Adam Miller
@millera023
What is the thought process behind having Line2D and LineSegment2D? They appear to be "mostly" the same thing.
Johan Larsson
@JohanLarsson
I think I dumbed Line2D don't remember
IIRC the definition for linesegment is a start and an end point
And a line just goes through a point with a direction
And a ray starts at a point with with a direction.
mathnet/mathnet-spatial#158
There was some activity ^
Still no package
Adam Miller
@millera023
I agree with your definitions, however Line2D does not reflect the definition you gave. I am just trying to get a gauge on what direction the whole library is moving towards.
Johan Larsson
@JohanLarsson
I think I implemented Line2D in an unfortunate way.
lately there has not been much direction
Have you seen system.numerics btw?
It looks pretty nice
Adam Jones
@Jones-Adam
LIneSegment2D is more or less a name change from Line2D to free up the namespace to implement LIne2D as per the definition Johan gave for a line. But since releases seem to be a blocking point, the sequence of change got rather lost
the idea was first LineSegment2D/3D. Then deprecate LIne2D/3D, then remove Line2D/3D. Then reintroduce support for actual geometric lines
It was envisaged to do this in separate releases to allow existing users of the library time to adapt their code... but that was back when we kind of thought we could do a series of releases in sequence, roughly one a month. Smaller evolutions