<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="Tiki CMS/Groupware via FeedCreator 1.7.2" -->
<?xml-stylesheet href="http://cinderella-geometry.com/lib/rss/rss-style.css" type="text/css"?>
<rss version="0.91">
    <channel>
        <title>Tiki RSS feed for forums</title>
        <description></description>
        <link>http://cinderella-geometry.com/tiki-forums_rss.php</link>
        <lastBuildDate>Wed, 08 Apr 2026 03:54:06 +0100</lastBuildDate>
        <generator>Tiki CMS/Groupware via FeedCreator 1.7.2</generator>
        <image>
            <url>http://cinderella-geometry.com/img/tiki.jpg</url>
            <title>tikiwiki logo</title>
            <link>http://cinderella-geometry.com/tiki-index.php</link>
            <description><![CDATA[Feed provided by http://cinderella-geometry.com/tiki-index.php. Click to visit.]]></description>
        </image>
        <language>en-us</language>
        <managingEditor>authors@cinderella.de</managingEditor>
        <webMaster>kortenkamp@cinderella.de</webMaster>
        <item>
            <title>CindyScript  local() does not work for nesting</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1056</link>
            <description><![CDATA[Using v2.9, build 1835, using local() for the same variable in multiple functions does not work:
test2() :=
(
  local (next);
  next = 2;
  err(next);
);
test1() :=
(
  local (next);
  next = 1;
  err(next);
  test2();
  err(next);
);
test1();

results in

next ==> 1 
next ==> 2 
next ==> 2 <<<< expect 1]]></description>
            <author>wdheker</author>
            <pubDate>Fri, 16 Aug 2019 12:45:44 +0100</pubDate>
        </item>
        <item>
            <title>Rendering from Media Browser</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1050</link>
            <description><![CDATA[I want to know if Cinderella is compatible with new Mac OS X El Capitan, because last year I could use the Media Browser to render files from my desktop, and now I don't seem to be able to get a response in Cindyscript.]]></description>
            <author>singerarts.com</author>
            <pubDate>Fri, 11 Mar 2016 02:14:02 +0100</pubDate>
        </item>
        <item>
            <title>How to finesse CindyJS</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1045</link>
            <description><![CDATA[An ordinary construction of points, lines, circles and five point conics can be saved as an interactive web page which uses JavaScript instead of the JavaVM.
Use "Export to CindyJS" from the File menu to create such a page.

1) You will notice that the dependent points are drawn using bright colors instead of the dim colors Cinderella uses.

To fix this, edit the generated web page and change:
^defaultAppearance: {},^
to
^defaultAppearance: { dimDependent: 0.7 },^
so the default color scale factor for dependent points is 0.7 instead of the default 1.0.

The defaultAppearance value has the following defaults:
^defaultAppearance: {
	dimDependent: 1,	// applies only to points
	pointColor:[[1, 0, 0],	// matches Cinderella's default point color (red)
	pointSize: 5,		// matches Cinderella's default point size
	alpha: 1,		// opacity for both point and line drawing
	lineSize: 2,		// if this were set to 1 then it would match Cinderella's default size
	lineColor:[[0, 0, 1],	// matches Cinderella's default point color (blue)
	clip: "none",		// line endpoint clipping; other choice is "end"
	overhangLine: 1.1,	// applies only to lines and then only if clip value is "end"
	overhangSeg: 1		// applies only to line segments
}^

2) The pos: [[ ... ], values are only needed for "Free" points including those on lines, circles and conics and for selection of point intersection results.

3) Fix-up for any circles with a fixed radius
Note that "CircleByFixedRadius" becomes "CircleMFixedr" and the radius value needs to be added.
You will need to get the radius value from the formula in a  "Construction Text" window.
Change (for example):
^{ name: "C0", type: "CircleByFixedRadius", color: [[ 0.0, 0.0, 1.0 ], args: [[ "A" ], size: 1, printname: "$C_{0}$" }^
to
^{ name: "C0", type: "CircleMFixedr", color: [[ 0.0, 0.0, 1.0 ], args: [[ "A" ], radius: 2, size: 1, printname: "$C_{0}$" }^
Also note that you are not able to stretch the circle, only move it. 

4) Freelines are drawn randomly. Refreshing web the page moves them about.

5) Depending on pos value PointOnCircle crashes when used with conic.
Instead of doing a "Reached refinement limit, giving up."
instead does a "Need to refine." and throws an
uncaught exception: RefineException
Removing the throw makes the code work with no discernable problem.
In src\js\libgeo\Tracing.js: 
^debug("Need to refine.");
requestRefinement();
...
throw RefineException;^

This example of a geometry value fails:
^	geometry: [[ 
		{ name: "A", type: "Free", pos: [[ 1.0909090909090908, -4.0, -1.1363636363636365 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true }, 
		{ name: "B", type: "Free", pos: [[ -3.0676691729323307, -4.0, -0.7518796992481203 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true }, 
		{ name: "C", type: "Free", pos: [[ 4.0, 0.30418250950570347, 0.3802281368821293 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true }, 
		{ name: "D", type: "Free", pos: [[ 4.0, -1.5771428571428572, 0.5714285714285714 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true }, 
		{ name: "E", type: "Free", pos: [[ 0.6857142857142857, -4.0, 2.857142857142857 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true }, 
		{ name: "C0", type: "ConicBy5", color: [[ 0.0, 0.0, 1.0 ], args: [[ "E", "A", "B", "C", "D" ], size: 1, printname: "$C_{0}$" }, 
		{ name: "F", type: "PointOnCircle", pos: [[ 4.0, 1.8808856876336117, 0.47544934794164406 ], color: [[ 0.0, 1.0, 0.0 ], args: [[ "C0" ], labeled: true } ],^

Changing the "F" pos value to [[ 4.0, -3.9959345057221376, 1.5715851232332456 ] makes the example display.

6) Generally there are mismatches for the type values.
For some of these it is just a matter of changing the value:
^"Parallel" -> "Para"
"AngularBisector" -> "angleBisector"
"ConicFoci" -> "ConicBy2Foci1P"
"IntersectionConicConic" -> "IntersectConicConic"
"Conic4P1L" -> "ConicBy4p1l"
"Conic1P4L" -> "ConicBy1p14"
"Conic5L" -> "ConicBy5lines"
"ConicFoci" -> "ConicBy2Foci1P" use index: 1
"ConicFociH" -> "ConicBy2Foci1P" use index: 2
(not in Cinderella) "ConicBy2p3l" use index: 1..4
(not in Cinderella) "ConicBy3p2l" use index: 1..4^
"LineByFixedAngle", "Dist", "EuclideanMid", "Dist", "Text", "ConicParabolaPL", "ConicInSquare" and "Arc" are not implemented yet in CindyJS.
For multiple point intersection results you can use the pos or index value to select an object from the output collection.
For all multiple conic results you need to change type from "SelectP" to "SelectConic" and add an index value to select a conic not a point from the output collection.

Some points and lines for making a complete geometry value with the conics below:

^		{ name: "A", type: "Free", pos: [[ 0.4112149532710281, -4.0, -0.9345794392523364 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true },
		{ name: "B", type: "Free", pos: [[ -2.5477707006369426, -4.0, -0.6369426751592356 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true },
		{ name: "C", type: "Free", pos: [[ 4.0, 1.2374100719424461, 0.7194244604316548 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true },
		{ name: "D", type: "Free", pos: [[ 3.225806451612903, -4.0, 3.225806451612903 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true },
		{ name: "E", type: "Free", pos: [[ 4.0, -0.6363636363636365, -1.1363636363636365 ], color: [[ 1.0, 0.0, 0.0 ], labeled: true },
		{ name: "a", type: "Through", pos: [[ -0.8988764044943821, 0.5800888424353282, 4.0 ], color: [[ 0.0, 0.0, 1.0 ], args: [[ "C" ], labeled: true, size: 1 },
		{ name: "b", type: "Through", pos: [[ -0.3168316831683169, 2.9702970297029707, 4.0 ], color: [[ 0.0, 0.0, 1.0 ], args: [[ "D" ], labeled: true, size: 1 },
		{ name: "c", type: "Through", pos: [[ 1.5866209262435678, 2.8301886792452824, 4.0 ], color: [[ 0.0, 0.0, 1.0 ], args: [[ "E" ], labeled: true, size: 1 },^

Fragments of geometry values for various conics:

^		{ name: "Collection__1", type: "ConicBy4p1l", args: [["A", "B", "C", "D", "a"] },
		{ name: "C0", type: "SelectConic", color: [[0.0, 1.0, 0.0], args: [["Collection__1"], index: 2, size: 1, printname: "$C_{0}$" },
		{ name: "C1", type: "SelectConic", color: [[1.0, 0.0, 0.0], args: [["Collection__1"], index: 1, size: 1, printname: "$C_{1}$" }],^

^		{ name: "Collection__1", type: "ConicBy1p4l", args: [["a", "b", "c", "d", "A"] },
		{ name: "C1", type: "SelectConic", color: [[0.0, 1.0, 0.0], args: [["Collection__1"], index: 2, size: 1, printname: "$C_{1}$" },
		{ name: "C0", type: "SelectConic", color: [[1.0, 0.0, 0.0], args: [["Collection__1"], index: 1, size: 1, printname: "$C_{0}$" }],^

^		{ name: "Collection__1", type: "ConicBy2p3l", args: [["A", "B", "a", "b", "c"] },
		{ name: "C0", type: "SelectConic", color: [[0.0, 1.0, 0.0], args: [["Collection__1"], index: 4, size: 1, printname: "$C_{0}$" },
		{ name: "C1", type: "SelectConic", color: [[1.0, 0.0, 0.0], args: [["Collection__1"], index: 3, size: 1, printname: "$C_{1}$" },
		{ name: "C2", type: "SelectConic", color: [[0.0, 1.0, 1.0], args: [["Collection__1"], index: 2, size: 1, printname: "$C_{2}$" },
		{ name: "C3", type: "SelectConic", color: [[1.0, 1.0, 0.0], args: [["Collection__1"], index: 1, size: 1, printname: "$C_{3}$" }],^

^		{ name: "Collection__1", type: "ConicBy3p2l", args: [["A", "B", "C", "a", "b"] },
		{ name: "C0", type: "SelectConic", color: [[0.0, 1.0, 0.0], args: [["Collection__1"], index: 4, size: 1, printname: "$C_{0}$" },
		{ name: "C1", type: "SelectConic", color: [[1.0, 0.0, 0.0], args: [["Collection__1"], index: 3, size: 1, printname: "$C_{1}$" },
		{ name: "C2", type: "SelectConic", color: [[0.0, 1.0, 1.0], args: [["Collection__1"], index: 2, size: 1, printname: "$C_{2}$" },
		{ name: "C3", type: "SelectConic", color: [[1.0, 1.0, 0.0], args: [["Collection__1"], index: 1, size: 1, printname: "$C_{3}$" }],^

^		{ name: "Collection__1", type: "ConicBy2Foci1P", args: [["A", "B", "C"] },
		{ name: "C0", type: "SelectConic", color: [[0.0, 1.0, 0.0], args: [["Collection__1"], index: 2, size: 1, printname: "$C_{0}$" },
		{ name: "C1", type: "SelectConic", color: [[1.0, 0.0, 0.0], args: [["Collection__1"], index: 1, size: 1, printname: "$C_{1}$" }],^

7) Clicking does not highlight anything.
So you do not always realize that you are really just dragging the nearest movable point.
The point being dragged does not jump under the pointer either but remains at a constant xy offset from the pointer while dragging it.

Best regards,
Alexander Elkins

Updated: Fri, 30 Oct 2015 22:55:16 GMT
Refers to [http://cinderella.de/CJS/build/js/Cindy-dev.js]
  Last-Modified: Wed, 07 Oct 2015 14:47:14 GMT
  Content-Length: 359193 bytes
]]></description>
            <author>aelkins</author>
            <pubDate>Thu, 29 Oct 2015 22:51:09 +0100</pubDate>
        </item>
        <item>
            <title>Save/Close/Load cycle shrinks every window by 14 pixels in height</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1038</link>
            <description><![CDATA[A very annoying thing happens when you save a construction, close all the associated windows and then later load it again. Every window that was open at the time the construction was saved opens again but with 14 pixels less in height. This includes all Euclidean, hyperbolic, spherical, and construction text windows. They all share one thing in common, a white status line with black text which initially says: "Move free elements by dragging the mouse". This white status line is exactly 14 pixels in height. Perhaps this is what is not being accounted for?

Also any additional Euclidean windows opened are all 14 pixels greater in height than the initial Euclidean window of a new construction. This suggests that the size of the initial Euclidean window is already 14 pixels smaller than it should be.

Also the spherical window's width is 1 pixel too small in width to fit all of the bottom buttons in one line causing the [[Ell] button to overflow onto a second line making the window 30 pixels greater in height than the hyperbolic window.

Windows sizes observed:

Cycle Euclidean.1 Euclidean.2 Hyperbolic Spherical Construction
New 696x581 696x595 416x765 416x795 416x518
1st 696x567 696x581 416x751 416x781 416x504
2nd 696x553 696x567 416x737 416x767 416x490

~~#0000CC:Observed using Version: 2.9 build 1783 (2015/08/03 18:17) running on Microsoft Windows 7 64-bit SP1 with Aero Style theme.~~

The windows sizes were measured using [[Alt-PrintScrn] pasted into mspaint.

Best regards,
Alexander Elkins]]></description>
            <author>aelkins</author>
            <pubDate>Fri, 16 Oct 2015 19:27:52 +0100</pubDate>
        </item>
        <item>
            <title>Reproducing Julia Sets example (Tiny Code Examples)</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1037</link>
            <description><![CDATA[The Julia Sets example (Tiny Code Examples) needs some critical information to be able to reproduce it. The image is as shown below.

{img src=http://doc.cinderella.de/img/wiki_up/Ex11.png width= height= align= desc= link="http://doc.cinderella.de/tiki-index.php?page=Tiny%20Code%20Examples" }

You will find it off the help menu:
Help > Cinderella Manual > CindyScript > Tiny Code Examples > Julia Sets
or in "The Cinderella.2 Manual" ISBN 9783540349242
Chapter 16 -- Tiny Code Examples, Julia Sets (page 411)
or click on the image above to see the online documentation.

The placement of the point "C" is critical. The following CindyScript provides the missing information:

^// in Initialization

createpoint("A",[[-1.53,-1.17]);
createpoint("B",[[1.37,1.15]);
createpoint("C",[[-0.21,0.69]);
^

In addition to what is shown:
^// in Draw

g(z,c):=z~np~^~/np~2+c;

julia(z):=(
  iter=0;
  while(iter<100 & |z|<2,
    z=g(z,complex(C.xy));
    iter=iter+1;
  ); 
  1-iter/100;
);

colorplot(julia(complex(#))
   ,A,B,startres->16,pxlres->1);
^

Then zoom in to see the image as shown above.

Best regards,
Alexander Elkins
]]></description>
            <author>aelkins</author>
            <pubDate>Sun, 20 Sep 2015 20:46:51 +0100</pubDate>
        </item>
        <item>
            <title>Construction file loads incompletely</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1036</link>
            <description><![CDATA[When an angle bisector of two lines is created, a hidden point of intersection is created. It is possible for that point to be deleted without also deleting the angle bisector itself. While the construction itself remains intact and functions as expected, saving the construction in this state results in a construction which will load incompletely. Specifically, everything in the "Construction Text" view from and including the angle bisector itself onward will not load.

Start a fresh Cinderella session.
Create two lines, a thru A and b thru B, so that they intersect in the view.
Use "Angular Bisector" to create a bisector of the two lines (a,b).
Open a "Construction Text" view.
Observe that the bisector line c shows AngleBisector(a;b;C).
Now use the point or the intersection tool to create the intersection point of the lines.
Observe that the "Construction Text" view shows the point C as Meet(a;b) and most importantly it is shown following the bisector line c AngleBisector(a;b;C) even though it is referenced by it!
Now click Undo remove point C.
Observe that the bisector line c remains.
Now create a point anywhere in the view even at the intersection point of the lines will do.
Use Move tool to move line a or b.
Observe that the bisector line c now shows AngleBisector(a;b;_), with the placeholder '_' replacing the reference to 'C'
Now create a few other elements.
Save as IncompleteLoad.cdy.
Close all associated windows.
Load IncompleteLoad.cdy.
Observe that only the two lines a thru A and b thru B remain.
Also observe that the "Construction Text" view (which was open at the time of saving) did not open.

This unfortunate behavior is particularly insidious because you have three lines which can be paired three ways to create the intersection point. You may then perhaps decide to change which pair to use using undo and only after completing a complicated construction, saving it and only after loading it find it damaged.

Also observe that if Delete is clicked instead of Undo to remove point C, the bisector line c is also deleted. This will come as a surprise to someone who may have created both bisectors only to have them both disappear when only the point was to be removed. Clicking Redo then restores point C followed by bisector line c in the correct order. However if both bisectors have been created, the point is restored following them, the wrong order.

Also observe that if after the intersection point C is created, the bisector is deleted, then clicking redo places it following the point C in the correct order. However now clicking undo makes the point disappear leaving a blank line ahead of the bisector line c in "Construction Text" view.
Moving line a or b makes the blank line disappear and the bisector line c now shows AngleBisector(a;b;_). The undo should have undone the redo deleting the line again.

It is likely that there are several coding errors involved here.
1) Creating the intersection point should have inserted it ahead of the bisector, possibly appearing very early in the construction.
2) Undo should find the element to be removed from the list rather than deleting based on some stale index position.
3) "Construction Text" view should be updated under these conditions.
4) There should be a reference count for elements so that they are not removed if it is not zero as a cross check on coding errors.
5) Undo needs to remember the state of an element's setInMacro() setting and restore it to the macro list rather than deleting it.

Mirroring a circle in a circle is another example of where undo is also failing:
Start a fresh Cinderella session.
Create two circles C0 about A and C1 about B.
Use the Mirror tool to mirror C0 in C1 which creates C3 Circumcirle(D;F;H) as shown in the "Construction Text" view.
Using the point thru line creates line l thru point K.
Click Undo once removes line l thru point K.
Click Undo again removes C3.
Using the point thru line creates line l thru point K instead of line a thru point C.
The elements used to construct C3 have not been deleted.
Nor will they be reused:
Click Undo once removes line l thru point K again.
Use the Mirror tool to mirror C0 in C1 which creates C3 Circumcirle(L;N;P) as shown in the "Construction Text" view.
Using the point thru line creates line u thru point Q instead of line l thru point K showing that more element names have been used up.

~~#0000CC:Observed using Version: 2.9 build 1783 (2015/08/03 18:17)~~

Best regards,
Alexander Elkins

]]></description>
            <author>aelkins</author>
            <pubDate>Sun, 20 Sep 2015 19:59:56 +0100</pubDate>
        </item>
        <item>
            <title>Linked appearance between elements of same and different constructions</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1035</link>
            <description><![CDATA[This reproduces the unfortunate behavior that I encountered while constructing something more complicated over time.
The steps here save to a different file each time .
That is not necessary to reproduce the behavior.
Only the Save/Close/Load cycles are needed.

Start a fresh Cinderella session
Create a circle C0 about point A
Create  three lines thru A
Use point to create one intersection point with the circle for each of the lines (a,b,c)
Save as LinkedAppearance-a.cdy
Close associated windows
Load LinkedAppearance-a.cdy
Create the other intersection point opposite point B
Inspector shows a white zero size point; change it to size to 5 & color lime & set labeled & identifier to E
Save as LinkedAppearance-b.cdy
Close associated windows
Load LinkedAppearance-b.cdy
Observe the other intersection point opposite point C is displayed in lime (it was not visible before the save)
Inspector shows color is lime, size is 5, labeled is set; change identifier to F
Save as LinkedAppearance-c.cdy
Close associated windows
Load LinkedAppearance-c.cdy
Observe the other intersection point opposite point D is displayed in lime (it was not visible before the save)
Inspector shows color is lime, size is 5, labeled is set; change identifier to G
Save as LinkedAppearance-d.cdy
Now change the color of any of the lime points (E,F,G) to yellow.
Now redraw the view (the easiest way to do this is to zoom by using the mouse wheel or doing any translate, zoom-in, zoom-out or fit of the view) .
Observe how all of the lime points are now yellow
Select any of the linked points (E,F,G) and in the inspector, clear "Labeled".
Observe how all of the (E,F,G) labels disappear only to return when "Labeled" set again.
The "Draw Border", "Point Size" as well as all font settings (Font,Size, Bold & Italics) affect all of the points when the view is redrawn.

Observe that if LinkedAppearance-a.cdy is loaded now, the other intersection point opposite point B already appears as a yellow colored size 5 unlabeled point.
This is why starting a fresh Cinderella session was necessary as the first step to get predictable results.
Apparently something is being shared between constructions so much so that when the color of the now yellow unlabeled point in LinkedAppearance-a.cdy is changed to cyan,
redrawing LinkedAppearance-d.cdy shows that its yellow linked points are now also cyan.

Observe that if either one of LinkedAppearance-b.cdy or LinkedAppearance-c.cdy is now loaded, all of the linked points (unnamed, E,F,G) in all of the constructions are now colored lime immediately.

The same behavior can be observed in "Angular Bisector" lines:

Start a fresh Cinderella session
Create  three lines thru A
Use "Angular Bisector" to create one bisector line for each combination of the lines (a,b,c)
Save as LinkedAppearance2-a.cdy
Close associated windows
Load LinkedAppearance2-a.cdy
Open a "Construction Text" view and click on the unnamed bisector in that view
Inspector shows a white zero size line; change it to size to 1 & color lime & set labeled & identifier to h
Close the "Construction Text" view
Save as LinkedAppearance2-b.cdy
Close associated windows
Load LinkedAppearance2-b.cdy
Observe that another unlabeled bisector line is displayed in lime (it was not visible before the save)
Inspector shows color is lime, size is 1, labeled is set; change the identifier to k
Save as LinkedAppearance2-c.cdy
Close associated windows
Load LinkedAppearance2-c.cdy
Observe that another unlabeled bisector line is displayed in lime (it was not visible before the save)
Inspector shows color is lime, size is 1, labeled is set; change the identifier to l
Save as LinkedAppearance2-d.cdy
Now change the color of any of the lime lines (h,k,l) to yellow.
Now redraw the view.
Observe how all of the lime lines are now yellow
Other linked setting also change as happens with the points example above

Observe that if LinkedAppearance-c.cdy is now loaded, all of the linked lines (h,k,l) in the LinkedAppearance2-d.cdy construction are now colored lime immediately.

Finally, just what elements are impacted by this behavior?
The presumption is that any element multiple possible output elements would be impacted.
The list would then be following:
Line and circle/conic intersections, two points.
Angular bisector, two lines.
Circle/conic intersections, four points or only two (no conics involved).
Ellipse by foci and point (the other solution of course is the hyperbola)

That these are involved can be shown using:
Two lines thru a point
The angular bisector of the two lines
A circle about the point
An intersection point of the circle and one of the lines
An ellipse by foci and point positioned to intersect the circle in four places
An intersection point of the circle and the ellipse

Then cycling Save/Close/Load and giving the identifier a non-blank name, and changing the setting to make the element visible.
Sometimes selecting the unnamed element requires using a "Construction Text" view.

The result, attached (__could not be attached__) here along with the other two construction sequences, is LinkedAppearance3-a.cdy thru LinkedAppearance3-g.cdy.

If the original bisector in LinkedAppearance3-g.cdy is deleted and the construction is saved as LinkedAppearance3-h.cdy, closed and reloaded it reappears unlabeled and lime in color.
Now the appearance of both angular bisector lines are linked with the other linked elements.
By deleting the original output elements and and using a Save/Close/Load cycle and setting their identifiers, it would be possible to link the appearance of all of them.

Beware that the window shrinks by 14 pixels in height (different unfortunate behavior :-) with each Save/Close/Load cycle.
Just open a new Euclidean view and close the original when the view becomes too small.

~~#0000CC:Observed using Version: 2.9 build 1783 (2015/08/03 18:17)~~

Best regards,
Alexander Elkins

PS: Attach File is not working here!]]></description>
            <author>aelkins</author>
            <pubDate>Sat, 19 Sep 2015 16:46:18 +0100</pubDate>
        </item>
        <item>
            <title>Issues regarding text elements</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1034</link>
            <description><![CDATA[This mostly concerns the behavior of the "Add Text" ([[ABC] button) to add and change text elements.

1) Text which has been docked to any side of the view jumps when edited.
 * Use click [[ABC] button, click in view, enter "Text" & click [[OK].
 * Click "Move Element" and drag the "Text" to any side of the view to dock it there (x or y position snaps).
 * Click [[ABC] button, click on "Text" and click [[OK] (changing the "Text" is not required to see the behavior)
 * Observe the "Text" jumps and is no longer docked (using the "Translate View" ([[<|>] button) and dragging in the display area confirms this).


2) Click "Move Element" and drag the "Text" to the upper-right corner.
 * Observe that the "Text" jumps backwards when this is done.

3) Multi-line can be created:
 * Click [[ABC] button, click in view, and click the [[<] button in the dialog and enter (use the [[Enter] key to place each successive number on a new line):
1
2
3
4
5
 * Then click [[OK] in the dialog
 * Click "Move Element" and drag this multi-line to any side of the view to dock it there.
 * Observe that if the text is moved by click-dragging on the lower lines, the position jumps down by the distance to the first line.
 * If dragging on the "5", the text snaps when it is far from the bottom edge, and the drag point snaps up one line each time it passes out of view at the bottom until it is being dragged by the "1".

4) When "Add Text" ([[ABC] button) is used to edit multi-line text the line breaks are lost.
 * The line breaks are also lost after clicking the [[<] button, entering multi-line text and then clicking the [[v] button.

5) Click "Move Element". When the text is selected by clicking on it, a white outline is drawn around it.
 * This outline then persists whenever the text is click-dragged thereafter.
 * However if the text is click-dragged (without first clicking on it) the white outline is not drawn around it.
 * The white outline should also be drawn around the text when the pointer moves over it.
 * Other elements highlight when the pointer moves over them and remain highlighted when click-dragged without first having to be clicked.

6) Ctrl-drag does not include text elements
 * Create a couple of text (not docked to the points or view edges) and point elements
 * Use Ctrl-A keystroke to select all
 * Observe that click-drag on one of the points with Ctrl key held down only simultaneously moves the points.
 * The click-drag on one of the texts with Ctrl key held down moves only that particular text.

7) The documentation for the re-positioning of the label of a point, line or segment is a bit sketchy (see "Moving elements").
 * Click "Move Element", hold down the shift key and drag the label of a point or line.
 * Observe the dim white line that appears while dragging the label (not mentioned in the documentation).
 * The label for a point can be positioned at a fixed (x,y) pixel offset from the point (maximum radius of 72 pixels).
 * The label for a line or segment can only be moved to either end or side of the line or segment (not mentioned in the documentation).
 * For the segment labels the position is a percentage of the distance between the endpoints (not mentioned in the documentation).

~~#0000CC:Observed using Version: 2.9 build 1783 (2015/08/03 18:17)~~

Best regards,
Alexander Elkins
]]></description>
            <author>aelkins</author>
            <pubDate>Thu, 17 Sep 2015 18:30:24 +0100</pubDate>
        </item>
        <item>
            <title>Resolution</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1030</link>
            <description><![CDATA[I am using Cindy Script to render color art  under the Colorplot function.  Is there any way I can get a higher resolution than the current 72 dpi]]></description>
            <author>singerarts.com</author>
            <pubDate>Mon, 01 Jun 2015 12:05:50 +0100</pubDate>
        </item>
        <item>
            <title>problem with saving my construction</title>
            <link>http://cinderella-geometry.com/tiki-view_forum_thread.php?forumId=1&amp;comments_parentId=1027</link>
            <description><![CDATA[Hi, I have recently changed to the MATE version of GNOME as my operating system and today is the first time I am using Cinderella since the change. 
The program seems to work fine until I try to save the window freezes and I cannot do anything, not even close the window, except for restarting the whole operating system. Please let me know whether there is a fix for this.

Thank you!
Dorette Pronk
]]></description>
            <author>DorettePronk</author>
            <pubDate>Tue, 24 Feb 2015 21:40:35 +0100</pubDate>
        </item>
    </channel>
</rss>
