Dear Users,

1. I once thought as below, but actually I will not do so, but introduce a new keyword OGEOMETRY just for DISP to display the geometry based on the orbit. I may introduce new keywords (OGEO, etc) for LINE to obtain these values.

=========================
1. A new flag ORBITGEO will be added to calculate/display geometric information based on the orbit. Currently SAD calculates the geometry from the coordinates except in SOL section. It is not very consistent. With ORBITGEO, it will calculate using the orbt everywhere. The antonym will be COORDGEO, which calculates based on the coordinate everywhere including the solenoid. Actually a lot of discussions can be possible on this issue...
==========================

Dear Users,

1. New keywords will be added for LINE:

"OGEO" Geometric-parameters of the orbit at the entrance of the component,
{{OGX, OGY, OGZ}, {OCHI1, OCHI2, OCHI3}}.
"GX", "GY", "GZ", "CHI1", "CHI2", "CHI3"
Each geometrical parameter.
"OGX", "OGY", "OGZ", "CHI1", "CHI2", "CHI3"
Each geometrical parameter at the orbit.


> Dear Users,
>
> 1. I once thought as below, but actually I will not do so, but introduce a new keyword OGEOMETRY just for DISP to display the geometry based on the orbit. I may introduce new keywords (OGEO, etc) for LINE to obtain these values.
>
> =========================
> 1. A new flag ORBITGEO will be added to calculate/display geometric information based on the orbit. Currently SAD calculates the geometry from the coordinates except in SOL section. It is not very consistent. With ORBITGEO, it will calculate using the orbt everywhere. The antonym will be COORDGEO, which calculates based on the coordinate everywhere including the solenoid. Actually a lot of discussions can be possible on this issue...
> ==========================

Dear Users,

1. As there is an obvious conflict in the keywords CHI1, CHI2, CHI3 in LINE, they are changed as:

"GEO" Geometric-parameters at the entrance of the component,
{{GX, GY, GZ}, {GCHI1, GCHI2, GCHI3}}.
"OGEO" Geometric-parameters of the orbit at the entrance of the component,
{{OGX, OGY, OGZ}, {OCHI1, OCHI2, OCHI3}}.
"GX", "GY", "GZ", "GCHI1", "GCHI2", "GCHI3"
Each geometrical parameter.
"OGX", "OGY", "OGZ", "OCHI1", "OCHI2", "OCHI3"
Each geometrical parameter at the orbit.



> Dear Users,
>
> 1. New keywords will be added for LINE:
>
> "OGEO" Geometric-parameters of the orbit at the entrance of the component,
> {{OGX, OGY, OGZ}, {OCHI1, OCHI2, OCHI3}}.
> "GX", "GY", "GZ", "CHI1", "CHI2", "CHI3"
> Each geometrical parameter.
> "OGX", "OGY", "OGZ", "CHI1", "CHI2", "CHI3"
> Each geometrical parameter at the orbit.
>
>
> > Dear Users,
> >
> > 1. I once thought as below, but actually I will not do so, but introduce a new keyword OGEOMETRY just for DISP to display the geometry based on the orbit. I may introduce new keywords (OGEO, etc) for LINE to obtain these values.
> >
> > =========================
> > 1. A new flag ORBITGEO will be added to calculate/display geometric information based on the orbit. Currently SAD calculates the geometry from the coordinates except in SOL section. It is not very consistent. With ORBITGEO, it will calculate using the orbt everywhere. The antonym will be COORDGEO, which calculates based on the coordinate everywhere including the solenoid. Actually a lot of discussions can be possible on this issue...
> > ==========================

Dear Users,

1. As a strange behavior is seen in BBOX directive of a Canvas widget to cause an error, a temporary fix is written to bypass the error. It occurs in occasion when a FrameLabel is drawn in a plot. The reason is not known yet. It may produce a strange message but will work.