Error in Re-Multisniping / Feature Request
Reported by Therese Telepski | May 1st, 2008 @ 08:09 AM | in 2.0 Full Release
I set up a multisnipe group, wone one item.
As I wanted two of those articles I markes all of the now unmarked articles and again choose 'Multisnipe' via the context menu.
The result was -- well, somehow unexpected.
Some of the items showed up with the old colour and snipe amount right away without any further dialog. About ½ of the items only showed a completely white MAX field (white background, no numbers).
Cancelling all appropriate snipes, deleting some unwanted items and then multisniping the remaining items again didn't change that behaviour.
When I then decided to manually snipe on the 'white' items one after the other -- they showed up as members of the original multisnipe group again; same background colour, amount entered manually.
Looks like the clear up after one multisnipe auction is one isn't complete but leaves remnanats that in part prohibit making this item part of a later multisnipe group.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Of course this also leads to a feature request:
The possibility to choose the number of items wanted when establishing a bid group. One set as default, but with the ability to also choose a bigger number.
Comments and changes to this ticket
-
Therese Telepski May 1st, 2008 @ 02:22 PM
Update:
A few hours later I had a bid going through within another bidgroup.
Some of the other members of that group had their snipes cancelled, but funny enough not all of them. About one third remained active with the same background colour and the same smipe price.
Therese
-
Therese Telepski May 2nd, 2008 @ 04:18 AM
Update 2:
After I won another auction in the re-multisniped group, about 18 items of that group cleared, two remained active -- still with JWB 2.0B2.
I'm going to report whether this holds still true for JBW 2.0B3.
Therese
-
Morgan Schweers May 3rd, 2008 @ 01:56 AM
- → Milestone changed from “2.0 Full Release” to “Features”
- → State changed from “new” to “open”
Greetings,
Tagging this as a feature request for now.
-- Morgan Schweers, CyberFOX!
-
Therese Telepski May 3rd, 2008 @ 11:18 AM
Update:
The glitch turned out to be still present in JBW 2.0B3.
One auction of a small multisnipe group with 6 items or so went through. 4 other were cancelled, one remained active and had to be disactivated manually.
Attached are the latest errors in log connected to that acution.
Sincerely,
Therese
-
Therese Telepski May 6th, 2008 @ 03:54 PM
Dear Morgan,
the same behaviour happened again this afternoon I'm attaching a screen shot and today's error logs so you get the idea.
Sincerely,
Therese
-
Morgan Schweers July 1st, 2008 @ 03:10 AM
- → Milestone changed from “Features” to “2.0 Full Release”
- → Tag changed from “” to “bug multisnipe”
Greetings,
I misunderstood... I'm making some fixups to that part of the code, but it seems like a pretty complex problem to replicate. :(
I'll poke at it some more...
-- Morgan Schweers, CyberFOX!
-
Therese Telepski July 1st, 2008 @ 07:23 AM
Dear Morgan,
whereever this behaviour stems from, the result is, that the items of a snipe group aren't completely and thoroughly marked as clean and no snipe.
It has happened so often in the meantime (and once resulted in getting two EM soccer balls where I only wanted to get one) that I turned it to a kind of habbit to manually wipe out remaining members of a multisnipe group.
To get a bit more in the interface details: Unless I manually cancel **all members** (active and inactive) members of a snipe group after a won auction, it (the group) somehow seemes to remain active. Even when I only mark the inactive items and right click -> Multisnipe again, there are instantly back with color and snipe amount without even any chance for me to enter either of them.
Sincerely,
Therese
-
Morgan Schweers July 1st, 2008 @ 10:51 AM
- → Tag changed from “bug multisnipe” to “bug multisnipe serious”
Greetings,
Okay... It sounds like it wasn't 'forgetting' that it had been part of a multisnipe group. A lot has changed in that code, and I have tried testing a bunch of different ways and it doesn't look like it does that anymore...
If you have a pattern of use that you can use to test that it doesn't do that anymore, I'd like to toss a pre-release version your way. Drop me an email, so I can send you a private pointer to it.
-- Morgan Schweers, CyberFOX!
-
Therese Telepski July 1st, 2008 @ 11:07 AM
Dear Morgan,
my mail is
it (at) art-promo (dot) de
And there still are a lot of bid groups in my list ...
Feel free to contact me at any time.
I'm going to report any results back to this thread to 'keep the admin together' at the place where it belongs.
Sincerely,
Therese
-
Morgan Schweers July 7th, 2008 @ 12:46 AM
Greetings,
Any word on the pre-release behavior?
-- Morgan Schweers, CyberFOX!
-
Morgan Schweers July 7th, 2008 @ 01:01 AM
- → Milestone changed from “2.0 Full Release” to “2.0 Beta 4”
-
Morgan Schweers August 7th, 2008 @ 12:58 AM
- → Milestone cleared.
-
Morgan Schweers August 30th, 2008 @ 10:27 PM
- → Milestone changed from “” to “2.0 Full Release”
Greetings,
This is an ongoing problem; moving it to the full release tracker.
-- Morgan Schweers, CyberFOX!
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
