I have mentioned this before, and it was not a very popular idea, but I would like to float the notion again of having the option, to have your cards come up with a quantity in parenthesis, rather than list the card several times over. When looking through lists for trades, you could see that a trader had (#272 Joe Smith (17)) seventeen cards of this player, rather than having his name listed 17 times or having to scroll down through 17 images to get to the next card. this would make trading easier, and checking card quantities in your collection easier. Some like the listing option to show a grade and value for each card, perhaps it could be an option to have it either way? Any Thoughts?
-------------------------------
"He stood there like the house by the side of the road, and watched that one go by." - Ernie Harwell
Each exception to the rule you add to this does two things:
1 - Makes the feature more robust
2 - Slows the database down (added code)
Next ecexption, if you have the condition logged. Then if there's any other thing in the detailed add.
Please understand, I'm not bashing the idea, or the exceptions. I actually would welcome the inclusion (if it is feasible and sustainable). I just want everyone to understand the implications of adding such underlying code to the system and why it might not be feasible to implement such a feature.
spikemg wrote:
I agree also.. Maybe somehow make an exception if you have multiple SN cards so they are listed separately ???
-------------------------------
-- Dan --
Note: I have currently stopped accepting transaction requests but I am not opposed to trading. Please see my profile for more info regarding this.
On a related note, it would also be nice to be able to add quantities to a collection by entering a number instead of using a pull down menu limited to 10. I have over 300 copies of some cards, which keeps me from entering my collection here.
I 100% am on board with this idea. I don't think it would add too much additional load time as it would be a simple linear O(n) search through whatever cards are listed on the screen (for all cards in list(if cardA == cardB then combine; else continue;)). This may take a few more milliseconds, especially if you have 1000 cards listed on your screen, but beyond that I can't see it adding too much time to the wait.
But Dan is correct that the more exceptions you add, the longer the runtime will take. For example, just an extra check to see if the card is serial numbered has a worst case run time of O(n), which bumps the total runtime of the routine to 2n -- still linear and probably not too bad, but you don't want to go overboard.
