• 0

    posted a message on WADDU - WoW Addon Updater
    I see I combined a couple issues with the program not displaying the updated remote version. The screenshot above shows that if the program can not retrieve the version number from your preferred mapping, it will display a question mark.

    The other issue is that there are instances where the program displays the correct version number in the Mappings area on the right, but in the main Addons area the Preferred Mapping column which should display the latest version, is completely blank. This happens with ButtonBin, MagicRunes and TankWarnings. Attached is a screenshot showing this.
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    There are a lot of instances where the "Preferred Mapping" column (which actually shows a version # of that addons preferred mapping) either displays a "?" or is blank. !BugGrabber for example shows a "?". Bartender4's is blank, even though if you click the addon to view Addon Details (on the right of the gui) the version numbers for each mapping are known and displayed.

    For a lot of libraries, the Local Version and Preferred Mapping cell is crammed with too much info and as a result, you can't see the version numbers easily. For example, LibBabble-Boss's cell has "3.0/Changlog-LibBabble-Boss-3.0-r150", which is too large for the cell and makes it very difficult to check version numbers to see if it has been updated. I'm wishing for the cell to only display the version number. Same for the preferred mapping cell.

    Maybe I'm misunderstanding previous posts, but it sounds like an option was added to update only those addons which have updates. However, I don't see that option. Just the usual "Update All Addons", which I thought updated all addons regardless of there being an update.
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    We <3 you, Roemer
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    Im getting the same behavior with a6.1

    I deleted all Waddu files and start fresh, as I do every time a new version is released.

    I click Check for Updates. It gets down to Broker_Clock and throws an error. There is no specific error message like I first reported in a5, I believe, where Capping gave the url error. All that is displayed is a generic "Waddu has encountered a problem and needs to close. We are sorry for the inconvenience". That thread stops, and the other two continue checking updates. One of the threads gets to ButtonFacade_simpleSquare and now that thread is frozen. I assume no error is visible, because the generic error window is already open. The 3rd thread continues checking for updates until it gets to Headcount. That thread stops and that pretty much ends it, since all threads are dead.

    I close and reopen the program and test checking Broker_Clock manually. In the Mappings area in the upper right, I can see it retrieves the version from Curse, a few seconds go by and the generic error pops up. It does not display a version number from wowace, so I assume it could not get one, throws the error, program crashes. No specific errors and all that's in the log is:
    11/8/2008 5:20:27 AM: Debug - Initializing ThreadManager with 3 Threads
    11/8/2008 5:20:27 AM: Debug - Thread #3: Starting
    11/8/2008 5:20:27 AM: Debug - Thread #4: Starting
    11/8/2008 5:20:27 AM: Debug - Thread #5: Starting
    11/8/2008 5:20:27 AM: Debug - Load Mapping from C:\Documents and Settings\Shank\Desktop\Waddu\mappings.xml
    11/8/2008 5:20:43 AM: Information - Thread #3: Version Check for Broker_Clock
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    a6:
    I can't really use it now, because it crashes on too many addons when checking versions.
    Broker_Clock
    ButtonFacade_simpleSquare
    Capping
    Headcount

    so far. There are probably more, but I have a feeling I could be here a really long time checking, crashing, ignoring, close reopen Waddu, check, ignore the next crasher, etc. Hopefully those are enough examples to see what's going on. I'm not sure what it is now, since some of those do have wowace project pages.

    Ignore seems to be working, as I can set them to ignore and it continues on to the next addon.
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    Ah, so that explains the Ignore situation. Thanks.

    Yes, I do use -nolibs. I'll take the personal responsibility of managing external libraries, if it means file system and bandwidth efficiency in the form of less files on the hard drive, smaller downloads from an addon server, absolutely no way an incorrect version can get loaded by the wow client, etc. Your explanation makes sense.

    I have also run across situations where the version string of an addon's local copy is in the form r583242 and the site's version number is say r26 or even a stable 4.1. The numbers are apples and oranges and I have to look up revision dates to see which one is the latest.

    Good call on the mappings file. I was wondering if it was actually downloaded each time and was going to bring that up.


    Glad I could help. You're doing great work.
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    Using a5 I notice a few things:

    When checking versions of the addon "Capping" an error window opens saying:
    Getting URL http://www.wowace.com/projects/capping/files/ failed: The remote server returned an error: (403) Forbidden

    I think that addon was removed from wowace projects, so that may explain it. That would just be a mapping update.

    However, more importantly, this error causes WADDU to crash.

    I set it to be Ignored to hopefully avoid the crash, but the program still checks for an update, crashing the program again. So, something is up with Ignore. The addon is highlighted yellow in the list. But, if I check the Ignored list in the settings, there is nothing listed.

    Something is goofy about the version checking of Libraries. All my Lib* addons show the latest update is a very old version. For example: It shows the latest LibCrayon-3.0 from wowace is r55678. That version is so old, it doesn't show up on the "latest files" list on the project page. Maybe this crappy wireless connection I'm on right now is a factor, but the other addons seem to be checked properly.

    Update: I checked this from my good connection at home. a4 also crashes when checking "Capping" (I assume whenever the program tries to access a bad mapping?). I get the same odd behavior with the Lib* addon version checking.
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    Yes, the addon gets updated. After the version checks all that's in the log is:

    11/1/2008 9:46:03 PM: Information - Thread #3: Updating Omen from wowace
    11/1/2008 9:46:04 PM: Information - Thread #3: Downloaded to C:\Documents and Settings\Shank\Local Settings\Temp\tmp2BE.tmp
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    Hm, I updated about 10 addons this morning and it happened so many times that I'm pretty sure it happened with every update. Some were wowace updates, some were Curse. The ArchiveContentForm window doesn't look like it's displaying anything important. In the main area on the left, there is nothing under "---Archive" and there is nothing in the grey area on the right. If I hit the "Open with 7zip" button at the bottom, it looks like it opens 7zip with no parameters, because it just displays the contents of the c: drive. This may be relevant: 7zip is not installed in the default c:/program files..." directory, but I did update that setting in the options.
    Posted in: Updaters
  • 0

    posted a message on WADDU - WoW Addon Updater
    What is the purpose of the ArchiveContentForm window that opens after updating an addon?

    I have a feature request: Changelogs

    Can you display the changelog for an addon before updating it? It's annoying when I see an update, check the changelog for the goodies and it's just a localization update. There's really no need to update the addon in that circumstance.

    Changelog summary at the end. After addons are updated, give a summary window with the addons' changelogs. This was a much appreciated feature in JWU.
    Posted in: Updaters
  • 0

    posted a message on Specialevents-Mount-2.0 Error
    Hm, I'm going to disappoint myself if that is the issue. First thing I do with errors is update the addon. However, I've been unable to find an update (or a project/download page for SpecialEvents-Mount-2.0.

    Hm, after doing more research, I've come across SpecialEventsEmbed, which contains SpecialEventsEmbed and all the other SpecialEvents-* addons. I updated the 9 libraries within and the error is gone. Thanks.

    Sorry for the noob post!
    Posted in: Libraries
  • 0

    posted a message on Specialevents-Mount-2.0 Error
    I am getting an error whenever I use a mount macro. The error:

    [20:32:01]2. [2008/10/22 20:30:36-3-x7]: SpecialEvents-Mount-2.0-59594:67: attempt to call global 'GetPlayerBuff' (a nil value)
    <in C code>: ?
    AceEvent-2.0-91091 (Ace2):298: in function `TriggerEvent'
    AceEvent-2.0-91091 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>


    The macro:

    #show
    /use [flyable] Swift Red Gryphon;
    /userandom Amani War Bear, Great Brewfest Kodo, Black War Ram, Black War Elekk


    Ace2 is version r1093
    Posted in: Libraries
  • To post a comment, please or register a new account.