Re: Solidmodeling using surfaces

barn_rubble@xxxxxxxxxx wrote:
This exact same story has played out so many times in the last few
years, it's just amazing to me that he still has the drive to keep
going.

Insanity is a crazy thing, ain't it? :)

Barn
http://blog.novedge.com/2007/07/an-interview-wi.html

Jon, Haywood, Craven, Rotnluv and the rest of the horrors living in Jon's
head ought to take a minute to get their stories straight.

They would have a little more coherence that way. I mean, how could you tout
a product that gets this response from tech support?

Quote

Hi Michael,
The reason we have used environment variables in VM 5.0 and RhinoCAM 1.0 is
to introduce functionality that would require GUI changes (Graphical User
Interface), without having to make the GUI changes. Since our product is
translated to over 5 languages this places undue burdens on the translators
to translate the new changes everytime we make a change to the GUI. So we
decided to use environment variables instead.

End Quote

and then

Quote

Hi Milton,
I am not sure what "optimized z-constant" means. A picture of the behavior
with and without the setting will help. In VM 5.0 we have an optimized
setting that will create cutter paths on flat areas during horizontal
finishing.

Depth first is turned on by default in VisualMill 5.0. To make it go level
first you will have to set up an environment variable called to force the
system to do this. This variable is:

VMILL_HFINISH_LEVELFIRST - 1/0 - Allows Level first machining in Horizontal
Finishing

To set Environmental Variables

a. Go to Start->Control Panel->System
b. From the System Properties dialog box that pops up select the Advanced
tab.
c. Click on the Environment Variables button at the bottom.
d. In the Environment Variables dialog box that pops up, click on the New
button under System variables
e. In the New System Variable dialog box that pops up, define
Variable Name = VMILL_HFINISH_LEVELFIRST
Variable Value = Set the value to 1

End Quote

How would you like to have to set a variable one way, run your post on
selected operations and then change the variable, run the other operations
and then manually kludge the two together to get a program that worked as
intended?

That is a lot more work that what Wayne did to get proper work shift support
in OneCNC. In fact, it's the definition of a non functional product. I'm
sure all of this will be adressed in the "next release".


Jon at least got one thing right. Joe and Anita are ordinarily pleasant
folks. Smart too so that's two things.
You couldn't, however, fill a thimble with what that entire bunch know about
the use their products see in the real world.
Like everyone, they will get their in due time and probably with a cool
product.


--
John R. Carroll

www.machiningsolution.com


.