Hi okapi - that problem is due to the history records that are generated on each of the lines.
Every time you run a command, the parameters of that command are stored on the output objects, so that it is possible to alter the inputs and replay the command to update the objects.
But in a case like this, the history data is actually pretty large since you had a large selection of objects that went into the command. When the record of your selection gets attached to all the output objects, it makes for a lot of extra data in this case. It is a lot of repeated data which is why it compresses so well in the .rar file.
One way you can fix it for now is to save to a file format that will not contain history, for example .igs format. Then if you read your curves back in from that .igs file the history data will be stripped and you should then be back to your original file size again.
I'll see what I can do to tune this up, probably for a couple of commands that may deal with a large selection of objects I should not store the history data on the output objects just for a few key commands.
Also for the next v2 beta I'll add something in to make it possible to set up a keyboard shortcut to remove history data.
For v3 I'm probably going to be trying to overhaul the history mechanism.
- Michael
|