>It would be beneficial if these links worked. At the very least make sure they appear in the main index.
>Also Dynamic Component function names and examples should be in a source code monospaced font. (Ie, a font without serifs.)
Want to do it?
Where the function names are headings, they should not be justified. (pg 346 for example look at the
Yes, I noticed that and am currently revising the whole document to fix justified lines
Another poor example is the bold paragraph on pg 332 with the code snippet below it. (Courier fonts are the ugliest possible monospaced fonts to use for code examples.)
Just a cut/paste, Buddy, just a cut/paste. If Trimble gives me some $$ I may build a real manual one day…
> Generally all the tables need some cell padding and a better font. (Looks like New Times Roman.) Column headings and descriptive text in tables should be the same as the font outside the tables, unless it is code function names or code snippets.
Ex: pg 353
Did these tables just copy and paste this way ?
Yes, they did, and I already removed all this sh*t to Verdana 10 black.
Thanks for your care.