I noticed what creating a new project that if I entered my account password incorrectly that the NEXT button would be disabled and wouldn't become re-enabled until I navigated back several screens.

STEPS:
NOTE: I've put BOINC Manager in advance mode
1. Select TOOLS | ADD PROJECT...
2. Select an project from the list that hasn't been previously chosen. In my case, I chose Asteroids@home.
3. Check NEXT button
4. Select the radio button, "Yes, existing user"
5. Enter a valid email but invalid passwords. Hit the NEXT button
6. After receiving the message about the account already being in use, hit the <BACK button.
7. Now that your back at the Account Screen, notice that the NEXT> button is disabled. Correct the password in the password field either by deleting the incorrect password for the field or retype a portion of it.

RESULTS: The NEXT> button still stays inactive

8. Click the back button again.

RESULTS: The NEXT> button is still disabled. Also, why is there a back button here since this is the starting screen for joining a project?

9. Click CANCEL button
10. When asked if you really want to cancel, select NO button.

RESULTS: The NEXT> is now enabled again.

I noticed this problem as well - but it is a problem with the BOINC software - not the asteroids at home module. You would probably be better off reporting this bug in the general BOINC software forums as per this link:

https://boinc.berkeley.edu/trac/wiki/ReportBugs

As for the password reset issue from the other thread - its another week down the road and still not resolved - and THAT issue *IS* on the asteroids@home side.

Good luck to you. Me - I've learned to live with the next button bug. I can still get things done - I just want to get them done on my MAIN account and not this sockpuppet wannabe account.

I think it is actually module based because I notice this isn't an issue with every module.
Yes, it's a small issue but I'm QA so you just feel a need to report issues w/ the hopes that they get resolved and it makes for a better product.

Thanks for the link to the BOINC link.

You're welcome!!

I ran into this issue quite a few times - I usually just cancel out and start over - however your comment got me thinking - was that with different modules or with the same one over and over?

Good eye on confirming its not with every module - attention to detail is a good quality for a QA guy! and you have displayed it there! - but before I stand corrected - I still fail to see the connection between the module and the BOINC software that is sending the request to the project.

My understanding is that the module doesn't actually do anything until it's downloaded and given a downloaded work unit.

Until that time - it's just the BOINC software establishing a connection and communicating with the project servers. For the project servers to have any control over the BOINC software after connection (like disabling (or if you extrapolate that- reprograming) a button) doesn't seem right.

However - before I go too far - I admit I am only aspiring to ever even get to amateur status as a coder - - so I could easily be missing something.

Bottom line - another thing that would be nice if it could be fixed by the actual developers - who I am sure are up to their eyeballs with other work.

Have a wonderful weekend! - look forward to some news next week.

Apparently this has been fixed in BOINC itself.

Please notice a new version of BOINC has been released and the link to the release notes is here:

https://boinc.berkeley.edu/wiki/Release_Notes_for_BOINC_7.12

Notice the 5th point under the change log for 7.12.0:

"Fix Next buttons in attach wizard after failed login."

The latest release is 7.12.1 - which apparently has also fixed:

"Fix auto-attach for Windows."

Now if we could just have the devs fix the password reset issue on this project...