BUG: Intersect can't use a variable as intersection index for 3D intersections
In both Geogebra 5 and 6 the Intersect command refuses to store an expression defining the intersection index when the intersection involves 3D surfaces (at least hyperbolic paraboloids, possibly all quadrics). Whatever expression I put there, it gets immediately evaluated to a number, and that number is stored in the definition.
This is inconsistent with the behavior for 2D intersections.
The way it hurts me is by preventing me from creating a tool that would accept intersection index as a parameter. Not being a Geogebra Merlin who can write tools in code, I must first create an example output object, and then use it to create the tool. However the intersection index argument gets hard-bound, and I have no way to specify it as an input when I create the tool; the variable where I put the intersection index is not offered as a possible input object, because the output object doesn't actually depend on it, having hard-bound its value at the time of definition.
I can't run 100m in less than 10". This is not a bug. And indeed Intersect can't handle with all possible types of objects either
intentalo en el adjunto con C en output
tengo como norma general crear todos los puntos interseccion y seleccionar el deseado, y me funciona
1) Take your rants to Twitter
2) don't be rude to other users
3) Please assume good intentions of everyone else here
If you can't do the above then you are not welcome on this forum
Comments have been locked on this page!