@mikko, How do you think about this?
Guides are currently stored in a way that isn’t tracked by the undo/redo mechanism. Feel free to add this to youtrack for future evaluation.
Instead of adding a wish for undo, I added a wish for combining AddGuides and RemoveGuides into a single command. I think that is more useful than supporting undo.
I agree. Rhino already has too many similar commands: Tweedledum and Tweedledee commands
In my opinion, it does not matter whether Undo and Redo commands ignore guides, but Purge command should be able to purge everything, including guides. At present, the Purge command ignores guides. If Undo, Redo, and Purge commands ignore guides, this fact should be mentioned in documentation.
Subject: BackgroundBitmap --Paragraph contains this sentence twice;
“Background bitmaps are always aligned with the x axis of the construction plane. If you want your bitmap rotated with respect to the construction plan, you must open it in a bitmap editing program and rotate it there, or you can create a rotated construction plane and place the bitmap on it.”
I removed the first duplicate from the help project. The we bpage will be updated when the next time I upload the help topics. Thanks.
The Purge command deletes UNUSED BlockDefinitions, Layers… etc. Guides don’t have the used/unused state.
Users will easily discover undo and redo are not supported when they try. If we want to document everything not supported, there will be too many to add. For example, we document a command is history supported instead unsupported.
ApplyMesh command is not explained well. It seems that it does not work, and it may be obsolete.
PointDeviation help does not include the select objects to extract points to test feature which was added in V6. It appears that the help description was not updated when the command was enhanced.
I’ll check. Thank you both.
It works as expected. Start the command, select a mesh (Do not press Enter) and select a surface.
I updated the topic with a gif animation.
Updated, please check. Thanks.
Looks reasonable. Thanks.
AttachGHSData documentation is posted here: https://docs.mcneel.com/rhino/6/help/en-us/commands/attachghsdata.htm
It mentions GHS, but it does not explain its meaning. GHS stands for General HydroStatics. It is popular program used for hydrostatic analysis of floating vessels.
It may be good idea to replace GHS with General HydroStatics in:
It says: AttachGHSData
Add GHS-specific information to objects.
I prefer: AttachGHSData
Add General HydroStatics information to objects.
I’ll check, thanks.
The command list is here: https://docs.mcneel.com/rhino/6/help/en-us/commandlist/command_list.htm
Each command name is linked to documentation of the command. One of the commands included in the list is MeshFromPoints. The name is linked to “Download MeshFromPoints for Rhino 5.0 x64” rather than documentation file.
Download MeshFromPoints for Rhino 5.0 x64 is here: https://www.rhino3d.com/download/rhino/5.0/meshfrompointsv5x64
MeshFromPoints documentation file is here: http://docs.mcneel.com.s3.amazonaws.com/rhino/6/help/en-us/commands/meshfromlines.htm#MeshFromPoints
The MeshFromPoints documentation file does not provide complete documentation because it does not mention command-line options.
GHS is a common term in naval architecture. My guess is many users of GHS data don’t know it stands for General HydroStatics. So my suggestion is
Add GHS (General HydroStatics) information to objects.
The link is fixed.
The command uses this mesh processing library that is not developed by our developers. Our developer can only speculate what the code does. I added the options and descriptions to the topic based on the speculation.
I chose to use @davidcockey’s approach in the start section of the topic and in the command list.
Thank you both.
The main purpose of Rhino program is making “clean” curves and surfaces, which means curves and surfaces which have minimum number of control points that are necessary to define the curves and surfaces. I just watched latest Kyle Houchens video (https://vimeo.com/311963098). At 16:15 he says that Offset command makes “terrible” curves because it roughly doubles total number of control points. Kyle is great instructor, but lacks complete knowledge of Rhino. The Offset command has Loose option which does not increase total number of control points. Kyle made the mistake because documentation of Offset command does not mention this fact.
I suggest that you add one sentence to the Loose option documentation about total number of control points.