Granted: The Closing Only Clubface -- a Hinge Action per 2-G and 7-10 -- translates into Maximum Compression. But, that fact doesn't put the Clubface alignment -- Zone #3 (Ball Control / Hands) -- into the Clubhead's Zone #2 (Club Control / Arms).
From the other side of the 'family' coin, Throwaway of Zone #2 Power destroys the Clubhead Orbit and, hence, Zone #3 On Plane Clubshaft Control and Hinge Action Clubface Control. But, that consequence doesn't rob the Hands of their Zone #3 Directional identity and relegate them to the Arms Power Zone.
There is but one detail to be provided:
Why was Hinge Action moved to Zone #2?
No doubt the answer is "Because Homer said so".
Accepting that as a satisfactory answer -- -- then why were the many then necessary editorial revisions not made? Said another way, why were the many obvious conflicts left unresolved? No doubt the answer to these questions is "Because Homer didn't make them".
Understood.
But then, Homer also didn't plan on dying that fateful day in Macon, Georgia, either. Nor did he plan on his preliminary revisions being posthumously published 'as is' 23 years later. No doubt he would have expected thinking people to make thoughtful decisions. Alas, 'twas not to be.
New readers may think this is 'Monday morning quarterbacking', but that is not the case. I received a copy of the proposed revisions more than a year before their publication and brought this specific issue (among others) to the public attention in these Forums. The publisher either didn't read my concerns or didn't care.
Whatever, the end result is a travesty.
Yes, not reconciling comments like "(And, any Hinge Action (10-10) IS Ball Control (Zone #3)." on page 121 of the 7th edition. One of the "end of year" TGM Summits should be used to resolve these types of errors. The community of AI's should insist on it.
All,
Any ideas on how to resolve this???
DG
Last edited by Delaware Golf : 09-15-2010 at 08:07 AM.
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
ERROR: The request could not be satisfied
504 Gateway Timeout ERROR
The request could not be satisfied.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) HTTP3 Server
Request ID: CYJ0yH9s5o_i4DhSHLfytivLbkaqW8M2qwPp81hdG_kzbywkxZSQtg==