@dharr I edited the code above as you suggested. Hilighted in green. There is a print statement at the end on ModuleLoad so added some "xxx" 's to it so I would know which one is printing. THe Inforlevel seems to control the print statement not what is supposed to be displayed from infolevel. Also message is displayed for any infolevel number 0,1,2,3,4. But at least I have some control over the message now.

restart

infolevel[RationalTrigonometry]:=0
 "xxxxDefault global settings:-

     GeomClr = "Blue",

      Prntmsg = true,

       Prjpsn = 3 can be set to 1,

      Normalgpt = 1 or set to 0, 

    Metric is a 3 x3 symmetric matrix defaults to the Identity 

    matrix "


              infolevel[RationalTrigonometry] := 0

with(RationalTrigonometry)

@dharr   Below outlines my package structure. I just can't get the infolevel system to work. I have tried (I think) both you methods.

Any ideas of where I am going wrong?

restart:
infolevel[RationalTrigonometry]:=3;
with(RationalTrigonometry)

RationalTrigonometry:=module()
    option package;
    
    export 
        AcuteObstuseQ,
#about 20 exports

# load = `Default global settings`;
     
local ModuleLoad, ModuleUnload,Colour_Test,Remequal, Dsp, pzp, xpsn, ypsn, zpsn, prnt,
        RMatrix, GMatrix, RProjM,`Default global settings` ;   #RelDPxyz, WhichMyType,
global  Metric,normalgpt, Prntmsg, prjpsn, GeomClr ;
 

ModuleLoad:= proc()
          
     uses TT= TypeTools;
     global _T1, _T2L,  _T2VR, _T3L,  _T3VC, _T3VR, _T4L, _T4VC, _MyType;
          #_a1:=1, _a2:=1, _a3:=1, _b1:=0, _b2:=0, _b3:=0 #GCb, GCg, GCr,xpsn, ypsn, zpsn,
     userinfo(2,RationalTrigonometry, "Default global settings:-\n GeomClr = ""Blue"",\n Prntmsg = true,\n Prjpsn = 3 can be set to 1,\n Normalgpt = 1 or set to 0, \n Metric is a 3 x3 symmetric matrix defaults to the Identity matrix ");
     GeomClr:="Blue";
     Prntmsg::boolean:=true;
     prjpsn::{1,3}:=3;
     normalgpt::{0,1}:=1;
     Metric:=Matrix(3,shape=symmetric,[[1,0,0],[0,1,0],[0,0,1]]);
  
     local 
     MyTypes:= {_T1, _T2L,  _T2VR, _T3L, _T3VC, _T3VR, _T4L,_T4VC},
     AllMyTypes:= MyTypes union {_MyType};
 
     g, #iterator over module globals
     e;
      ModuleUnload:= proc()
     local T;
          for T in AllMyTypes do if TT:-Exists(T) then TT:-RemoveType(T) end if; end do;
          return
     end proc;
     alias (eparm=CircleParmUHG,LinePts=Lines);   
    
     TT:-AddType(_T1, {algebraic,symbol});
     TT:-AddType(_T2VC, 'Vector[column](2, algebraic)');
     TT:-AddType(_T2VR, 'Vector[row](2, algebraic)');
     TT:-AddType(_T2L, [algebraic $ 2]);
     TT:-AddType(_T3VC, 'Vector[column](3, algebraic)');
     TT:-AddType(_T3VR, 'Vector[row](3, algebraic)');
     TT:-AddType(_T3L, [algebraic $ 3]);
     TT:-AddType(_T4L, [algebraic $ 4]);
     TT:-AddType(_T4VC, 'Vector[column](4, algebraic)');
     TT:-AddType(_MyType, MyTypes);

     :-print("xxxxDefault global settings:-\n  GeomClr = ""Blue"",\n   Prntmsg = true,\n    Prjpsn = 3 can be set to 1,\n   Normalgpt = 1 or set to 0, \n Metric is a 3 x3 symmetric matrix defaults to the Identity matrix ");
     return
end proc;


$include "Rational_Trigonometry\Acute Obtuse Quadrances.mpl"

#about 20  $include....

end module:

@dharr   I have made some progress. I would like to structure the TOC so that the main package commands are directly under the Rational Trigonometry heading i.e. TOCtop. Then I have two sub packages UHG and RT Projective. I would like these to be under TOCsub1 and TOCsub2 rsspectivels.  Have tried several modifications to do with std2 & children () but no luck yet.

What would you suggest?

Edit:- I have being wondering about structuring the help files for the sub packages is sub folders and doing a seperate database document for each.

Download Help_Edit_to_Database_2023.mw

@C_R I removed Java because I don't really need it. That has definately made Explorer a lot snappier. Don't get the white page for 5-10 secs.

Double clicking on a Maple file to open is better, but some do just hang Maple with the white window. I left it for 10 mins to see.

@C_R Explorer has also strated handing for 10 seecs or so. Java is a good clue here. It installed a Jave viewer (I think) less than a month ago when I was looking ast how to export 3D plots for 3D pdfs. Shall remove that tonight when I get home and let you know.

Edit:- Maple always starts from the task bar. Rarely use the start menu for it

@acer Oh good. Nothing complex then. I had tried {colour,color}. Didn't work. 

@acer  "...a double printing of qqf,q13,q24".  I meant that it would tabulate the values and then also return them seperately onto the screen,

@acer  I am most supprised that 

DocumentTools:-Tabulate([columns,[qqf,q13,q24]],'width'=55);
  return qqf,q13,q24

don't produce a double printing of qqf,q13,q24.  Because that is exactly what I didn't try.

I have altered the proc so Tabulate is inside the if statement.

QQFProj := proc(q12::algebraic, q23::algebraic,
                q34::algebraic, q14::algebraic,
                {columns:=[QQFproj,Q13proj,Q24proj]},  prnt::boolean:=true) 
  description "Projective quadruple quad formula and intermediate 13 and 24 quads. Useful for cyclic quadrilaterals";
  local qqf,q13,q24, sub1,sub2,sub3, R;
  uses  DT = DocumentTools;
  sub1:= (q12 + q23 + q34 + q14)^2 - 2*(q12^2 + q23^2 + q34^2 + q14^2) ;
  sub2:=-4*(q12*q23*q34+q12*q23*q14+q12*q34*q14+q23*q34*q14)+8*q12*q23*q34*q14;
  sub3:=64*q12*q23*q34*q14*(1-q12)*(1-q23)*(1-q34)*(1-q14);
  qqf:=(sub1+sub2)^2=sub3;
  q13:=((q12-q23)^2-(q34-q14)^2)/(2*(q12+q23-q34-q14-2*q12*q23+2*q34*q14));#check this
  q24:=((q23-q34)^2-(q12-q14)^2)/(2*(q23+q34-q12-q14-2*q23*q34+2*q12*q14));#check this
  if prnt then
  DT:-Tabulate([columns,[qqf,q13,q24]],'width'=55);
  return qqf,q13,q24
  end if;
  return qqf,q13,q24
end proc:

@dharr I have just returned to this. Thank you for the work you put into finding out what can be done. I too found that Maple would only export 3D objects not lines points or text. I don't know whether this is a file type restriction or a Maple export limitation. Maybe an enhancment request should be submitted for this type of functionality.
 

@dharr Thank you. I will spend the next night or so studying that.

@WD0HHU 

simplify(res) assuming `real`

@acer The timing differences are striking. I need to do more of the tests on my own code.

@acer That is a great answer. I tested it and it so far is working in the package. 

In the code below why does :-align not have the unevaluation quotes,

                                             symbol has nothing

                                            'color'  doesn't have  :-  

Qdim := proc(P1, P2, {Q:=[ NULL,:-align={':-left'}]},
                     {vec1::list:=[NULL,:-align={':-below',':-right'}]},
                     {scale::{list,numeric}:=1},
                     {leader::{-1,0,1}:= 1},
                     {dimoffset::{1,2,3,4,5,6}:=1},
                     {point::list:=['color' = ':-blue', symbol = ':-solidcircle', 'symbolsize' = 8]},
                     {line::list:=['thickness'=3]},
                     {plopts::list:=[]})

While I am asking al lot of keywords in 1d input are enclosed in the single back quotes ` ` but what do they actually do? Sometimes it seems to make no differance whether they are used or not. I know the are also used in prefix notation too.  

@acer Ok so what I have here with the procedure is outside of the package. So that may be affecting things.

I have altered the parameter names annotated in in the worksheet. Now `clr` is changed to `colour` that causes a clash. `Colour` works. `points` changed to `Point` not working. I can solve the problem. I was just trying to come up with sensible names. I was concerned about my capatilised names conflicting with other packages also I wasnted to keep them lower case if possible. @Carl Love indicated that this would not be a problem inside a package.

I will probably settle on names such as pointdata, linedata, message::boolean =true instead of prnt="y" 

2024-03-09_Example_parm_names_changed.mw

@acer Basically I don't know using nicer, parameter names suck as line, point, and colour, and print (I am sure print clashes)will clash.  Hopefully this will demonstrate sufficiently.  

Download 2024-03-09_Example_parm_names.mw