AutoCAD 2000/2000i/2002 Archive (Read Only)
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Reply
Message 1 of 6
Anonymous
366 Views, 5 Replies

HIDEPRECISION

I have some deep philosophical issues with HIDEPRECISION. Why does it always
revert to zero when I open a drawing in which it was previously set to 1?
Why would I *ever* want it set to zero? And if I'm working on a particularly
complicated drawing, why can't I set it to say... ten (or eleven, because
that's one higher)?
5 REPLIES 5
Message 2 of 6
Anonymous
in reply to: Anonymous

Read the online help. Here you find the answers to all your questions:

1st: Hideprecision is not stored (neither in the drawing nor in the
registry). Therefore you must set it in each drawing again. The default
value is "0".

2nd: Hideprecision is only a "toggle". Hides can be calculated in double
precision if it is set to 1 (uses more memory and more calculation time)
or in single precision (if hideprecision = 0) -> less memory needed,
less calculation time consumed, but also less precision. Therefore it is
nonsense to set hideprecision to 10 or 11 or whatever ... 😉

Regards
Juergen


David Wilde wrote:
>
> I have some deep philosophical issues with HIDEPRECISION. Why does it always
> revert to zero when I open a drawing in which it was previously set to 1?
> Why would I *ever* want it set to zero? And if I'm working on a particularly
> complicated drawing, why can't I set it to say... ten (or eleven, because
> that's one higher)?
Message 3 of 6
Anonymous
in reply to: Anonymous

I'm sorry if my initial query was unclear. I understand the 0/1 = on/off
nature of the command, and online help is great for answering "how?" But I
did not use the word "how" in my post. What I am interested in is "why?" Why
is hideprecision not stored? And why is hideprecision not scalable? ie.
triple, quadruple, etc. precision. This is why I have asked this question of
knowledgeable people like yourself, instead of a machine database.

David

"Jürgen Palme" wrote in message
news:3B7956D6.49653EB8@debitel.net...
> Read the online help. Here you find the answers to all your questions:
>
> 1st: Hideprecision is not stored (neither in the drawing nor in the
> registry). Therefore you must set it in each drawing again. The default
> value is "0".
>
> 2nd: Hideprecision is only a "toggle". Hides can be calculated in double
> precision if it is set to 1 (uses more memory and more calculation time)
> or in single precision (if hideprecision = 0) -> less memory needed,
> less calculation time consumed, but also less precision. Therefore it is
> nonsense to set hideprecision to 10 or 11 or whatever ... 😉
>
> Regards
> Juergen
>
>
> David Wilde wrote:
> >
> > I have some deep philosophical issues with HIDEPRECISION. Why does it
always
> > revert to zero when I open a drawing in which it was previously set to
1?
> > Why would I *ever* want it set to zero? And if I'm working on a
particularly
> > complicated drawing, why can't I set it to say... ten (or eleven,
because
> > that's one higher)?
>
Message 4 of 6
Anonymous
in reply to: Anonymous

I am not a programmer but I can imagine that programmers pride themselves on
making really fast applications. Hiding lines is a source of many machine
cycles. In pursuit of a fast program I am sure that the single precision
arithmetic that gives passable results is preferable to double precision
arithmetic that gives better results. That is assuming speed is the goal, and
you can be sure that speed is one of the goals. I can see why they would want
the variable set to fast.
All I did is add the line:
(setvar "hideprecision" 1)
to the end of my acad2000doc.lsp file in the support subdirectory. I added it
as a separate line just before ;;Silent load.

David Wilde wrote:

> I have some deep philosophical issues with HIDEPRECISION. Why does it always
> revert to zero when I open a drawing in which it was previously set to 1?
> Why would I *ever* want it set to zero? And if I'm working on a particularly
> complicated drawing, why can't I set it to say... ten (or eleven, because
> that's one higher)?
Message 5 of 6
Anonymous
in reply to: Anonymous

Doh! I never thought of that. Thanks!

"Peter Smith" wrote in message
news:3B79E5DB.1CC9D669@mindspring.com...
> I am not a programmer but I can imagine that programmers pride themselves
on
> making really fast applications. Hiding lines is a source of many machine
> cycles. In pursuit of a fast program I am sure that the single precision
> arithmetic that gives passable results is preferable to double precision
> arithmetic that gives better results. That is assuming speed is the goal,
and
> you can be sure that speed is one of the goals. I can see why they would
want
> the variable set to fast.
> All I did is add the line:
> (setvar "hideprecision" 1)
> to the end of my acad2000doc.lsp file in the support subdirectory. I
added it
> as a separate line just before ;;Silent load.
>
> David Wilde wrote:
>
> > I have some deep philosophical issues with HIDEPRECISION. Why does it
always
> > revert to zero when I open a drawing in which it was previously set to
1?
> > Why would I *ever* want it set to zero? And if I'm working on a
particularly
> > complicated drawing, why can't I set it to say... ten (or eleven,
because
> > that's one higher)?
>
Message 6 of 6
skiz
in reply to: Anonymous

IT WORKS!! Thank you!! I've been looking for this answer for weeks.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report