Failure to quit.
Creates duplicate tabs.
Sluggish [read; slower than a retreating glacier with like responses]
Similar behaviour in prior versions resulted in total loss of archived, or
completed, listings. On this most recent occasion, after force quitting
and re-launching, I found that release 1.06pre retained my completed
auctions. I culled about 10% from the completed tab list and then
deleted the errors logs from .jbidwatcher - bringing it's file size down
from 500 MB to 250 MB. The 75 errors logs accounted for 175 MB.
The apparent result, JBW has stabilized.
Not elegant but efficacious.
Alternatives?
Wondering if it's possible (and if so, how?) to export completed listings
for independant archiving and maybe even autonomous, from JBW,
viewing of completed auctions?
Best,
Mike
Logged In: YES
user_id=19745
Originator: NO
Greetings,
Bugs filed before 1.0 and bugs without responders are being juggled in terms of priority (9 is highest priority). I'm raising bugs filed with a submitter, post-1.0 to P6. Bugs which are filed post-1.0, but without a submitter are P5. Before 1.0 bugs with a submitter are becoming P4, and pre-1.0 bugs without a submitter name become P3.
If the bug is still relevant, and has a watcher (i.e. you got notified when I changed this bug), feel free to bubble it back up again.
Email addresses in bugs are great, but I can't always respond via email. Sometimes, especially for duplicate bugs, I use automated tools (like I'm doing right now) to change status on a large number of items at once.
Thanks for your patience, while I try to pare back the bug list to what may actually still be in the program.
-- Morgan Schweers, CyberFOX!