JBidwatcher Forums are in Read-Only mode for a server move

2 issues in JBidwatcher (2.1pre7-8-g61363f2)

Subscribe to 2 issues in JBidwatcher (2.1pre7-8-g61363f2) 12 post(s), 6 voice(s)

 
Avatar Liam 16 post(s)

Running JBidwatcher (2.1pre7-8-g61363f2) on MacOS 10.6.3

1. The “Seller” info is showing wrong in JB.

Example:
097S03382 512MB XEROX PHASER MEMORY 6300 6350 7400 8550 (380228436944)

Price $23.50
Seller – opens in a new window or tab
Listing ends at Thu May 27 10:33:41 EDT 2010

2. Some auctions are showing in JB as Buy it Now, with the snipe disabled.

Example:
14 BOXS 336 K CUPS KEURIG COFFEE TEA ICED HERBAL DECAF (390199200333)

Price $63.00
Shipping $0.00
Seller a question
Listing ends at
Fri May 28 16:01:41 EDT 2010

On Ebay page is has: Bid history: 6 bids[Refresh bidhistory]
Current bid: US $63.00

I quit and restarted, and it’s the same. I noticed it today, My Completed history has the correct seller name, the last entry in Completed is dated 3 May 2010.

Cheers, Liam

 
Avatar clinky 2 post(s)

I’ve been using 2.1pre7-8-g61363f2 on Mac OS X 10.5.8 since it came out. After about a week, I started experiencing the same problems with the seller names that others have reported: “a question” or “- opens in a new window or tab” appears instead of the seller name for about 80% of the sellers.

Also, my “Won” items, which were appearing correctly in blue after installing 2.1pre7, stopped working properly (now appear in red, not recognizing me as the winner) at about the same time as the seller name issue appeared.

I’m assuming these are both problem related to how eBay is handling member names.

 
Avatar Morgan Schweers Administrator 1,200 post(s)

Greetings,
I’m just letting folks know, I’ve pushed up a 2.1pre7-28-gcd0e285 version to the same download spot described here and will be releasing it as a 2.1pre7 officially tomorrow evening, unless some showstoppers come up.

So…please try it out and let me know if there are any showstoppers! :)

It fixes…snipes failing, bad seller names, bad bidder names, auctions seen as fixed price, unable to retrieve prices, selection color customization, private listing recognition, some sticky search and update infinite loops, and it reduces the amount of derby.log data dumped out when debugging is set to true. There’s also a bunch of improvements internally, and some work towards a new feature that a bunch of users have been asking about.

Yeah…there’s a lot of code in there.

It’s about as tested as I can manage personally, so I’d love some more eyes on it! Feedback is all I ask…!

Best of luck with your auctions!

— Morgan Schweers, CyberFOX!

 
Avatar Philip 34 post(s)

Morgan

Thanks for the new version.

Have tried 2.1pre7-28-gcd0e285 on Windows 7 64-bit, and the Selection Colour is still not working for me – I get a dark blue background with black writing on it, which is all but impossible to read.

 
Avatar Morgan Schweers Administrator 1,200 post(s)

Greetings,
Sorry I wasn’t clear; it makes it possible to customize the selection color, it doesn’t change the selection color by default.

You can customize the selection color by following this FAQ: http://www.jbidwatcher.com/help/faq#ans28

Best of luck with your auctions!

— Morgan Schweers, CyberFOX

 
Avatar Philip 34 post(s)

Morgan

Many thanks! I’ve set it to your suggested value (C6A646) and it works really well.

Two minor suggestions for the FAQ:
1) For some reason, this question is answered twice in there (Q15 and Q29)!
2) You need to exit JBidWatcher and restart it before the new value is applied (at least I did) – it may be worth mentioning this.

 
Avatar Liam 16 post(s)

Hi Morgan – I downloaded from the link above, and am running JBidwatcher (2.1pre7-29-g519c99a) . Auction 190400691880 is showing in JBidwatcher as a Buy it Now, and not as an auction.

Cheers, Liam

 
Avatar Morgan Schweers Administrator 1,200 post(s)

Greetings,
@Liam – This should be fixed in the most recent version (2.1pre8 at this time).

— Morgan Schweers, CyberFOX!

 
Avatar frost5709 7 post(s)

Has anybody else noticed that pre7 and pre8 seems to be really, really slow? It starts out being pretty responsive to UI interactions like changes in the tab, entering new auctions, etc. but then it just gets slower & slower. After a couple of hours it takes >5 seconds to respond to a click on the scrollbar. I haven’t tried sniping with this version yet so I don’t know how much the slowdown will affect that. I had a large number of expired auctions and since the loading of finished auctions never completed I suspected that that was the cause but I deleted a large number of those and it is still slow even tho now it completes.

I’m using the Windows executable and Java 1.6.0.70.

 
Avatar budney 2 post(s)

I’m seeing this slowness, and it’s driving me nuts because I’m using JBidwatcher to buy diabetic care supplies, and it keeps missing auctions because it’s so dog slow.

Here’s how I observed the problem. First, I created a new tab and called it “Test Strips.” Then I created a search, updated hourly, for “aviva strips,” that put the results on that tab. I enabled the setting to remember deleted auctions. So every hour, more auctions appear on the tab for test strips for my Accu-Check Aviva. I look them over, delete the ones I don’t want, and set a snipe amount for the rest. It didn’t take long before this incredibly awful performance started showing itself. Killing and restarting helps, but you have to do that once an hour, which defeats the entire purpose of running JBidwatcher.

I’m using 2.1-pre8 on a Macbook.

 
Avatar budney 2 post(s)

Update: now I’m fairly convinced that it was caused by “My JBidwatcher.” I tried turning it off many times in the preferences and it would be right back on after restarting… but after editing the config file directly and deleting my username and password, performance has been solid for the last 18 hours.

 
Avatar frost5709 7 post(s)

We have a winner! I tried disabling MyJbidwatcher by editing the configuration file and now 2.1pre8 runs normally. Thank you, Budney! I kind of suspected that this was due to some obscure difference in my configuration or in how I use JBidwatcher since evidently not everyone is having this problem.

I played around with MyJbidwatcher a little about 6 months ago but never got it working properly. So maybe my particular non-functional setup is partly to blame.