code recycling - Thursday, October 22, 2009Split into two objects. One for drawing and editing the polygon. A second macro object for calculating all polygonal stuff around arcs etc.
Implemented arcs defined by tangents.
Big changes - Wednesday, October 14, 2009Another big step forward. Concept of segmentation style is changed. It is prepared for 3 different arc definition methods and two Bezier segment types. Of course beside straight an (new) NO segment. Yes, Bezier! I decided to include this type of shape from the beginning, not later, when I decided to create the CURVE-macro. At least it is prepared now to include it later completely. My main focus is now to finish a first stable version with two polygons of "parallel" polygons.
This will lead to the first spin of to realise an object, which stretches bitmaps on a freeform plane in 3D. With this object you will be able to generate a 3D model out of two, three or more bitmaps straight without an AddOn. Still future music, as we say in Germany, but not so far away, I hope.
Back to the news: 3 point defined arcs work well so far. If the 3rd point of the arc definition is the exact midpoint between the bordering corners or identical with one of them, a straight segment will be output. If the corner is set to be a straight segment, the 3rd point is preset to the midpoint (without function, of course).
Maximal aberration defines segmentation of each arc segment. Because "parallel" polygons may have different radius in each arc I calculate it for each segment separately. I programmed it first in this way, that the complete segmented polygon will be calculated after each change of the constructing nodes. This caused problems, if each segment of each polygon in one set has to be separated in identical number of approximating (max. aberration) parts. This is necessary e.g. to realise a editable RULED-object. It created very large array parameters, too. Anyway. I discarded this way. Solution: After each change of a corner or any other shape defining parameter the following values will be calculated and stored in a parameter: ARC-midpoint, -radius, -beginning angle, -end angle and the number of seg
Bugfixing - Wednesday, October 14, 2009Arcs whose border points share the same X or Y value did not work proper (Malfunction of exeption/zero definition of TAN-function part). Solved by a new case investigation and a dirty workaround with an endless inclination.
One big step forward - Wednesday, October 14, 2009New try and big step forward: Found a cardinal spline algorithm. Prepared for a common polyline macro. Found a segment reducing algrithm.
Vectorfont and UI - Thursday, July 12, 2007Implemented the vectorfont for corner labeling and UI added. Buttons for arc and bezier section added. Edge vivibility button too.
Multiple Polygons - Wednesday, July 04, 2007Implemented first multiple polygon set. One can adjust any number of polygons with identical number of nodes. Inserting a new edge inserts one at the same position (dividing half the distance) in the rest of the polygons too. Origin of each polygon is independant moveable. Unique hotspot IDs fixed to each edge: After inserting a new edge dimension strings will keep correct associated to the objekt (ArchiCAD 11+).
First working version - Thursday, June 28, 2007First version, wich works without jumping nodes or malfunctional hotspots. After I thought I have it on 7th of June, now it works! Puh! Prepared for multiple polygons. Will become a battle of parameters!
Merged object starts - Thursday, June 07, 2007For programming an editable boundary for the
curve-makro I awake two older tries (2004/2005) of graphical editable polylines. One, which I wrote for concrete plate is partly obsolete, since GS ships a poly-macro with its basic library.