Dear forum visitor,
It looks as though you have not registered for a forum account, or are not signed in. In order to participate in current discussions or create new threads, you will need to register for a forum account by clicking on the link below.
Serena McTavish
Active Member
Problems: It's too easy to accidentally contribute hundreds or thousands KP by hitting max button. When player wants to contribute an amount between 1 and max, player must hit the 1 button repeatedly.
Potential solutions:
1)Combine the min and max KP donation buttons in the AW contribution window . Replace two buttons with a single button that accepts a number where you can type in the donation amount. See included image below.
2) Add a 3rd KP button , between the 1 button and max button , which accepts a number where you can type in the donation amount
3) Relocate the max button away from the 1 button. This only reduces chance of accidental donation and doesn't fix having to repeatedly click the 1 button. This change requires the least amount of coding.
Benefits:
1) prevents accidentally contributing the max kp amount which could be hundreds or thousands of kp.
2) makes it easy to contribute a larger amount between min and max without clicking on the "1" button many times.
Cons - possible implementaion effort:
Programming changes should be minimal and straight forward for both display and calculations. The existing software already calculates the possible max based on what space is left on the AW and how many KP a user has.
Combining the two buttons circled in the attached image and replacing with a single button requires changes to the display code and would need code to accept data entry.. That button would have integer entry field so that player can enter exact amount. The "free" kp would display over the top of this button and would disappear once used as it does today. The number entry field would accept an integer between 1 and the max amount that has already been calculated. If the player doesn't have any KP, the button would be greyed out or have a diamond cost that's calculated based on the player input. All software would behave as it does today.
Adding a new button could reuse existing code for calculating the maximum amount that could be contributed. The button display code could be reused and modified to included data entry and it would behave as described above. The "free" kp button would not display over this button- it would still be over the existing max kp button.
Relocating the max kp button would require changes to the display code.
Potential solutions:
1)Combine the min and max KP donation buttons in the AW contribution window . Replace two buttons with a single button that accepts a number where you can type in the donation amount. See included image below.
2) Add a 3rd KP button , between the 1 button and max button , which accepts a number where you can type in the donation amount
3) Relocate the max button away from the 1 button. This only reduces chance of accidental donation and doesn't fix having to repeatedly click the 1 button. This change requires the least amount of coding.
Benefits:
1) prevents accidentally contributing the max kp amount which could be hundreds or thousands of kp.
2) makes it easy to contribute a larger amount between min and max without clicking on the "1" button many times.
Cons - possible implementaion effort:
Programming changes should be minimal and straight forward for both display and calculations. The existing software already calculates the possible max based on what space is left on the AW and how many KP a user has.
Combining the two buttons circled in the attached image and replacing with a single button requires changes to the display code and would need code to accept data entry.. That button would have integer entry field so that player can enter exact amount. The "free" kp would display over the top of this button and would disappear once used as it does today. The number entry field would accept an integer between 1 and the max amount that has already been calculated. If the player doesn't have any KP, the button would be greyed out or have a diamond cost that's calculated based on the player input. All software would behave as it does today.
Adding a new button could reuse existing code for calculating the maximum amount that could be contributed. The button display code could be reused and modified to included data entry and it would behave as described above. The "free" kp button would not display over this button- it would still be over the existing max kp button.
Relocating the max kp button would require changes to the display code.
Attachments
Last edited:
[Happy Dance]
