I've coded a roster application in ASP.NET that allows ratings in different skill sets to be recorded for each player in a softball league to help optimize draft picks.
Presently, there are 160 players in the league and there are 3 skills defined (running, batting, defense). That's 480 star ratings generated by a template field in the GridView object.
The page will allow around 40 ratings to be assigned and then each ratings control altered after that doesn't set the "CurrentRating" property with the same yellow stars, but it does display the rating we've chosen with the red "waiting" stars that are ment to only be displayed during a mouseover event.
Saving the initial 40 ratings and leaving the page enables another 40 yellow ratings to be set before the same bug occurs. My question: Has anyone encountered this issue on a web form that's heavily populated with the Rating control defined in the Ajax Toolkit and, if so, have you discovered a simple fix for this bug?
Obviously, one fix would be to enable paging on the GridView. However, the end user who requested this web forms app be developed has a low level of computer literacy, so I'm trying to limit the number of moving parts so as to keep the app as user-friendly as possible.
The solution I'm currently working on is tracking the number of ratings changed, then triggering a PostBack when 40 ratings have been assigned and saving those changes as session data. Hopefully, this will simulate the assign 40 / save ratings/ leave and return to the page workaround.
I thought surely someone else has encountered this issue before and might have some insight into the origins of this particular bug, or at the very least come up with a more elegant fix than my Automated PostBack idea.
Code not included because the issue is with the Ajax Toolkit control itself and not code I've written for this app.
Aucun commentaire:
Enregistrer un commentaire