BZ 1633: Hitter type choice appears when clicking next on player editor

[Curtis]

When in the player editor you cannot simply click on the next/previous player to change players. You have to click on him (the name or arrow), which brings up a menu for changing (I assume) the current player to a spray, normal or pull hitter. After a pause you can then click on the name or arrow again, and the player editor page will change.

Aside from the inconvenience of having to click-pause-click, instead of just click, every time it happens (and it happens every time), I'm worried that I'll either changed the batting style of a player… or that I just did.

I saw another couple of arrow issues, which I'll mention here rather than start two more threads (this is already my third):

In the pages of game summary after playing out a game, one of the pages (the pitch-by-pitch summary) has the 2006 double set of back-and-forward buttons/arrows instead of the 2007/8/9 single set, and they don't work. Clicking on either set has no effect.

If you're on a player editor page and backspacing takes you to that same player's front page (the page that appears when you click on his name), that front page has no next player/previous player arrows or names. The positions normally occupied by them are occupied by the scouting pulldown, which has shifted right from where it's normally located. The next player/previous player arrows are where they should be if you access the same page from any screen other than that same player's editor.

[Tony M]

Hi, sorry for the delay in a reply.

I have seen this issue before on my PC version. If after editing a player you might be down in the fielding area on the right hand side and that's what causes the hitter type to pop up on clicking the arrow. If you scroll the right side back up to the top, the arrow should work properly.

[Curtis]

Yes. Since I don't know any other way to link to it:

This thread is located at:
http://www.ootpdevelopments.com/boar...-new-post.html


I saw your initial response and checked it out. You were right about it only happening when the screen was scrolled down. The other two issues were not addressed and probably should be ticketed. For that matter, I would think the issue you responded to would be deserving of a ticket, since it's still not working properly despite the workaround.

By the way, I'm not being notified of all of the responses to my posts. Your response in this thread, for example. If I hadn't decided to check out all of the support threads I've originated recently this one would also probably have been closed due to lack of response.

[Tony M]

Logged as BZ 1633