Jump to content

Adam Sternberg

Members
  • Posts

    61
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Adam Sternberg

  1. @Fred Slota, I never received an answer on why the file was download from the forum servers as 0 bytes. Would you like me to try to get you the files directly? Do you have a Dropbox or Google Drive I should upload the file to?
  2. @Fred Slota, the genie cartoon was Shazzan, with Kaboobie the flying camel!
  3. Fair point. I'd asked Mark before and recall he'd said it was OK, but it's just as easy to post here or on Slack
  4. This title is wrong. I've corrected the spelling of League, added a space after the colon, and submitted the correction. I wanted to post here, just in case they don't go through properly.
  5. @Fred Slota, my apologies. I don't know what happened there. I tried downloading and saw that it was 0 bytes as well. However, on the link page itself, it says the page is the file size is 49 kB, which matches what I have locally. @Steven L. Dasinger, do you know if there's someone I can contact to troubleshoot this? For example, can someone check the zip file on the server?
  6. The various printings look to be all over the floor in terms of Notes and/or Item Descriptions. I'm current on updates and just ran rebuild lists, so should be all up-to-date. There's nothing in the item description fields, and some of the notes fields say it collects issues 1-6, others say it collect 1-2, and the first printing (Bk 1) actually says both! Looks like the Collector's Set printings also suffer from this (and maybe even the Deluxe Set issues). Just to add insult to injury, the Bk 1 third printing has the same UPC as the first (I own that one, but don't have access to it for now to check). I'm afraid this needs a good spring cleaning, but I'm afraid I don't have access to the various issues to straighten it out. Can someone here (or on the Editorial Team) straighten it out, please and thank you?
  7. Honestly, I find the information in Item Description useful when I'm working on cover artist corrections to match up variant with the artist it goes with. Sometimes the cover artist information is not correct (against what's printed in the credits in the actual issue) but the info is in the Item Description
  8. Terrific! I'm glad to see someone using it!
  9. Well, THAT only took almost a year instead of "a week or so". Unfortunately, there were some changes to the exported reports used as input data that requered some redesign, and it took waaaaaaaay longer than expected. Shows what shrinking free time will get you... @Fred Slota, I've uploaded the fixed version here: Thanks for your patience, and I hope it fits your needs. Adam
  10. Version 1.3.0

    495 downloads

    The original Collection Hole Finder tool, updated for ComicBase 2020 and later Collection Hole Finder came about as effort to enhance ComicBase's ability to list issues missing from a collection (essentially, issues having a Quantity value of 0). While the ComicBase Issue Checklist report applied to missing issues is useful, it is often overwhelmingly large, especially when considering some older titles, such as Action Comics. While any collector will determine that any missing issue is a hole that needs to be filled, I determined that a pragmatic solution was needed, and decided that I would focus on filling holes of finite size. What is a hole? A hole is a grouping of missing issues between issues owned. For example, if I own issues 1 and 5, then the hole is issues 2-4. I settled on a hole size of 5 issues or less. If I own issues 1 and 5, then I'd try to buy issues 2, 3, and 4 eventually. However, if I own issues 1 and 7, then forget about issues 2-6. Once that decision was made, I could export the missing issues checklist just for those titles I had "in stock" into a spreadsheet and start deleting issues that didn't fit into a small enough hole. However, that still meant whittling a report of thousands of issues down to one of tens of issues by hand. Since I'm a programmer for a living, it seemed natural to create a program to parse the text file output from ComicBase. And so, Collection Hole Finder was born. Later on, in the ComicBase forums, others posted with similar frustrations, and it was requested that Collection Hole Finder be shared with other collectors. I was encourage to share the source code with the users, in the hopes that they could recommend (or even code up) enhancements to the program. Please see the "Contact" section to recommend enhancements or share changes.
  11. These are the same issue. One of them should be removed, although I have no real clue as to which one should be removed (probably Annual 2020).
  12. This title doesn't really exist. Instead, it's really part of B&V Friends Forever. Compare https://atomicavenue.com/atomic/item/1016642/1/BampV-Friends-Forever-Summer-14 with https://atomicavenue.com/atomic/item/1048852/1/BampV-Friends-Forever-14 . I propose that B&V Friends Forever: Summer be removed.
  13. This issue doesn't really exist, although 2 and 3 do. Instead, issue 1 is Spider-Man: Brand New Day - Extra!! #1. Compare https://atomicavenue.com/atomic/item/1029180/1/Amazing-SpiderMan-Extra-1 with https://atomicavenue.com/atomic/item/420186/1/SpiderMan-Brand-New-DaymdashExtra-1 . I propose that Amazing Spider-Man: Extra #1 be removed.
  14. Probably already too late, but I added and submitted those issues last night.
  15. @Steven L. Dasinger, I know it's work, but I think it will still be helpful: not everyone has Archive, so wouldn't be able to make use of Feature 1 (and maybe not Feature 2, either).
  16. @Mark J. Castaneda, in the past, I've submitted title corrections (for right or for wrong) by changing the information and submitting corrections on one of the issues (the thought being the changed title information would be submitted as part of the issue submission). Would that not work?
  17. Someone mistook the shared cover credits on the alternate cover of The Joker (3rd Series) 7/A as individual issues, so each cover artist (the cover artist, cover inker, and cover colorer) were credited with a separate issue. I've corrected 7/A, and both 7/B and 7/C should be deleted.
  18. To answer @Gregory Hecht's question, there is no continuity really between these books. There be some between a couple of books, or even sub-series here and there, but overall, there isn't any.
  19. @Gregory Hecht, on Windows, "control T" brings up the "Titles" pop-up. There's also the folder icon in the upper right (between the "Previous Title" and "Next Title" triangle arrow buttons)
  20. Douglas Johnson is right about Gregory Johnson and Steven Johnson being right! 😁
  21. FWIW, I know if an issue were delayed for whatever reason, the street date doesn't always get updated with the changed date (there were a number of issues (including Marvel) that were deferred from last year due to the pandemic) . Could that explain what you're seeing?
  22. If you know where the HTML log files that are generated when the update runs are kept, you can open it directly (it will still be there from your last update, so may not need to re-run it).
  23. @Andrew d’Entremont, the livestreams also go up on YouTube; I'm unable to watch live as well, but I usually watch a day or two later on YouTube.
  24. @Steven L. Dasinger, good memory! That was indeed me, and I do still have it. @Fred Slota, it's been several years since I worked on it, so it may need some tweaking and recompiling, but I think it still good. Caveat emptor, your mileage may vary, etc., etc., but if you're willing to be a little patient and give me about a week, I'll work on cleaning it up and posting it. (I didn't realize we had a downloads section in the new forums, or I'd have done this sooner!)
  25. I've noticed some strange behavior with the update logs in build 21.0.1.1671 when updating content using Sidekick vs. within ComicBase itself. I have three databases that I maintain and update weekly through Sidekick. The update logs generated all have the name of the first database in the queue (which happens to be the default ComicBase Database.cbdb) in the log filename. However, when I update from ComicBase, the log has the name of the database open (in this case, Default ComicBase Database.cbdb) is in the log filename. The same also is true of the name of the database listed in the log itself. Either the filename variable isn't populating correctly when generating the log, or the log for the first update operation is getting created multiple times.
×
×
  • Create New...