andyson:@PRS Better, but you're going to still get complaints about having to click SPIN to get to the spin dot. Is SWING going to be active without selecting a club? The game needs to know which club first before assigning applicable shot types.
I think they'd be complaints about any change. Having put some thought to it I think something like this might work best...

Instead of having 3 steps just having 2.
Default before selecting a club is avatar in upright pose (as in the picture above or as per andyson's mock-up).
Step 1 - CLUB is highlighted green as above. When the player selects club the following happens > the avatar changes to avatar holding selected club pose > the word CLUB changes to the club name (brand, pic etc) > SWING turns green.
Step 2 - SWING - When the player selects the swing type the word SWING changes to the type of swing > the distance in YDS appears
'Ball on the tee' (spin) stays exactly the same.
The only exception is putting where Step 2 isn't required. Upon selecting the putter the distance in YDS/FT would appear.
lonniescott711:Your suggestion is too costly , it would require changing graphics as well as rewriting code and new program
IMO that's speculation. It would require changes but I'm sure WGT developers have a handle on what they would need to change to improve the interface and whoever decides budget would have an opinion on what's 'too' costly or not.
While WGT developers would say these are 'big changes' for them to work on they're going to be fairly minor changes from what players have been used to but those changes will be noticeably better.
2DAMFLASHY:sorry but i dont get why some want it changed,,,?
it's not just change for the sake of change but an improvement posted to the product suggestions thread.
The suggestion in essence is getting rid of the autocaddy. Following up on that, once you've got rid of autocaddy things would look different; so we're looking at the interface and how that might change. These are ideas that we're just putting out there and any others are welcomed.