2024 Technology Preview Program:
Master powerful new features and shape the latest BIM-enabled innovations
2012-07-30
11:21 PM
- last edited on
2023-05-26
02:26 PM
by
Rubia Torres
2012-09-05 01:00 AM
2012-09-05 01:21 AM
2012-09-05 08:30 AM
2012-09-05 10:05 PM
PB wrote:Yes--now using Lion on a MBP 15" retina.
Dave, your signature shows a Retina MBP......are you now using AC16 on this, & have your problems disappeared?
2012-09-07 12:47 AM
Dave wrote:I will look a little deeper to see if there is a change between the two but upon testing it just now I don't see a difference in behavior. A possibility that a migrated work environment from a previous version is in the mix?
This only malfunctions for me in AC 16. Still works fine in 15.
Dave wrote:I will see about reviewing the help documentation and see if we can improve it.
I've been using AC long enough that I can usually figure out any issues that come up, but I've been referring to the HELP pages quite a bit the last few days and have come to realize that they leave a lot to be desired. The explanation for those controls could definitely be explained better.
Dave wrote:If there is indeed a bug we will investigate it. You are welcome to contact us directly at "support at graphisoft dot com"
Because logic wasn't working for me, I have tried every combination of the tracker and coordinate input settings with no joy.
2012-09-07 07:13 PM
NCornia wrote:Using Tracker without the Coordinates Palette gives me exactly the same (incorrect) results. This is what happens: Choose the Line Tool (Polyline, etc.) - Click to start - keyboard entry A - enter value - keyboard R to set length and the A value in Tracker reverts to 0 or if using surveyor's unit, reverts to N 90 E. I've experimented with every combination of settings in WE>Tracker & Coord. Input with no change in results. I would like to remedy this soon, as it is a huge pain in the posterior to draw property boundaries.
Dave et al,
My recommendation for users going forward is to use the Tracker but it's not a mandate.![]()
2012-10-30 03:10 PM
2012-11-28 02:28 AM
2013-01-16 06:41 AM
Dave wrote:So, Graphisoft has been able to reproduce this problem. We've also discovered why some folks suffer and others do not experience the problem. In WE > User Preference Schemes > Tracker and Coordinate Input, selecting the "Prefer polar coordinates in Tracker..." option turns on the bad behavior--and it doesn't seems to be reversible. Unselecting it and drawing results in AC misbehavior.NCornia wrote:Using Tracker without the Coordinates Palette gives me exactly the same (incorrect) results. This is what happens: Choose the Line Tool (Polyline, etc.) - Click to start - keyboard entry A - enter value - keyboard R to set length and the A value in Tracker reverts to 0 or if using surveyor's unit, reverts to N 90 E. I've experimented with every combination of settings in WE>Tracker & Coord. Input with no change in results. I would like to remedy this soon, as it is a huge pain in the posterior to draw property boundaries.
Dave et al,
My recommendation for users going forward is to use the Tracker but it's not a mandate.![]()
2013-04-10 11:17 PM
Dave wrote:One further note on this issue: You must enter the length of the line first, then the angle. If you enter the angle first, then hit R to enter the length, the angle reverts to a bad number.
So, Graphisoft has been able to reproduce this problem. We've also discovered why some folks suffer and others do not experience the problem. In WE > User Preference Schemes > Tracker and Coordinate Input, selecting the "Prefer polar coordinates in Tracker..." option turns on the bad behavior--and it doesn't seems to be reversible. Unselecting it and drawing results in AC misbehavior.
The problem has been passed along to Budapest. In the meantime, there does seem to be a workaround, though I don't believe it worked in AC 15 (where I first noticed this problem). If you enter N 45 15 E for the angle, the result is correct--that is, do not enter N45 15E as you are supposed to be able to do, but include a space between the compass points and the numbers.
If that doesn't work for you, please post here. I'm not sure when this became a viable workaround, because I tried this and countless other gymnastics in the past with no luck, but it has been working for me without fail for about a week now.