Jump to content
AutoDesSys

Numeric input box lost upon pan or placement of guideline


AsOne

Recommended Posts

Numeric input box is no longer highlighted upon panning or placement of guideline.  This is a bug that has persisted since the beta of v7!!!  It actually causes me a lot of trouble:

 

1.  It is really time consuming to mouse up or hit tab several times to re-highlight the box.  Multiply this many times over in a day and I waste a lot of time dealing with this bug.  Then multiply it by about +/-5-7 years (whenever v7 beta came out) and that is a lot of wasted time.  

 

2.  If I Reshape an object, pan around and visually get it close to the amount I want, then I type in an exact number, then hit enter (but do not remember to re-highlight the box) - the point at which the object is reshaped is NOT the numeric input, but whatever point my mouse ended up on screen.  In other words it is totally wrong.  Often while I am moving quickly it is hard to notice the mistake.  I then copy or use this incorrect object for other operations, not realizing its inaccuracy until later.   Same thing happens in Move/Copy tool and other tools, it isn't just Reshape.

 

I will just keep posting this bug until it is fixed.

 

Am I the only one who has issues with this??? 

Link to comment
Share on other sites

I will relate a story regarding this issue:

 

I recently recommended a fellow architect check out FormZ as an alternative to SketchUp.  They played around with it and told me it was totally inaccurate and inconsistent.  They couldn't figure out why nothing was exact.  The would enter 10' and get 9'2 11/16" or enter 10' and get 2".  Then sometimes it would work and 10' was actually 10'.  They could not figure out what was going on.  They asked me for help and (forgetting this bug that I'm sadly used to by now) it took me a while to figure out the problem myself.   I then explained the issue to them...lets just say there was a laugh and they said "I think I will stick to SketchUp".

 

It's a small detail, but the devil is in the details as they say.  Personally I would rather have the next update (8.7 or whatever it is called) be the iPhone "S" cycle update.  No huge new fancy tools, just improvements, stability, and bug fixes.

 

Link to comment
Share on other sites

Am I the only one who has issues with this??? 

 

 

I run into this daily.  I think the input palette is poorly deisgned--length, width, and height/distance appears and disappears when called for various tools (and don't all show up at the same time) but the X,Y,Z coordinates are always editable.  

 

Perhaps strictly using the X, Y, and Z coordinate system was an old way of modeling, and at times it is useful, but I think there is to much emphasis on these text fields instead of L, W, H/D.  I'm not saying L, W, and H/D should be showing at all times, but the coordinates most definitely do not need to be editable at all times.

 

Maybe the solution to this would be to not have an "Input palette" but instead have a "Coordinates palette" and when creating something all inputs are in the Tool Options palette.  This is arguably the most important palette in the program, so why not put all modeling inputs there?  The text fields are already there for certain tools.  Look at any of the tools in the Generate palette.  Instead of making L, W, and H/D text fields appear in the input palette, have them work in the Tool Options palette.  

 

In this case, if you hit Tab it will only scroll thru the text fields in the Tool Options palette.  If you want to tab thru the coordinates, the user will have to click in a Coordinates (formerly Input) palette text box.

post-37070-0-18031600-1519050027_thumb.jpg

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...