oh, I never intended to build this with a compound miter saw...they are not really good for this sort of fine work. I fully intend to build a special crosscut sled for my table saw for this. The wood will be high end stuff and I want zero chances of making a mistake! I am thinking about building a cheap version from cheaper materials first and selling it just to get the experience.

The reasons for getting it right in SU first was to check out how different woods and accents would look like.

Well that most definately did it. The issue must be in the tolerances. The compound miter joint calculator that I used is right on as far as the geometry is concerned. I think SU has some issues with small angle tolerances.

Thanks!

I have been trying to create a new design for a piece of furniture. No matter what i do, my parts do not join at the compound miters properly. I seem to always have a approx 1/32" gap.

I have change all the accuracy settings and this has not helped. I have attached the file if anyone wishes to take a look. The box is created by taking "boards" and putting in a 14.511 deg crosscut and beveling this line at 43.08 deg.

Any suggestions? Is this a round off error bug?

Thanks,
Chris

compound mitered box

I would also be very interested in this. I have a odd "color defiencency" that is related to red/green colorblindness. I can generally see pure red and pure green but shades of colors give me fits!

I am not so sure that it is random....I just removed item [0] of a 13 item set. Then, I added that particular edge back to the set...it went back in the orginal index position of [0]!

I have been playing around with this interface some some and found something that I consider to be a bit odd. The selection object stores the selected items in a way that seems to be unrelated to the order in which they were selected. It is just one of those "this is not right" thoughts....

Thanks Todd! I never could have imagined that the spelling was different!!!! I REALLY feel stupid now.....................

I am using the RDE to make my SU Ruby script. I got a strange issue today: elseif was not a recognized keyword in the RDE but is listed in the ruby documentation. I could not get the code to run until I made nested if/then/else/end blocks. Anyone else seen this?

Chris

I have worked in AutoCAD for years and am very familiar with this command process. However, the user interface for SU is so completely different. Your commands depend on the tool selected, not the previous task. For instance, you create a line and finish...you should still be using the line tool at this point. It does not go back to a generic command line like ACAD.

In essence, you are ALWAYS repeating the last command unless you change it...right?

I actually found this implied in an example in the length class API. If you use a float, the math comes out like you would expect. The Length class is where this changes (as Al suspected). Notice that the 0.001" value that I got while testing is not mentioned as a limiting factor.

@unknownuser said:

<
The < method is used to see if one length is less than another length.

Syntax
status = length1 < length2
Arguments
length1 - a length value

length2 - a length value

Return Value
status - true if length1 is < length2; false if length1 is not < length2

Comments
For example, if l1 = 1.0.inch and l2 = 1.000001.inch then l1 == l2 so l1 < l2 should return false.