• 0

    posted a message on Inline Aura - display aura information inside action buttons
    I was wondering if there could be some improvements made to the way Holy Power is handled for spells which provide a buff to the player, e.g. Inquisition. If I have any Holy Power charges, the display of that replaces the display of the duration of the Inquisition buff.
    Posted in: General AddOns
  • 0

    posted a message on WoW UI Updater 1.9 Thread (Windows/OSX/Linux, multiple sites)
    Hey lejordet, I don't know if you noticed, but the Qt GUI toolkit is now LGPL: http://www.qtsoftware.com/about/news/lgpl-license-option-added-to-qt
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater 1.9 Thread (Windows/OSX/Linux, multiple sites)
    What does "Update local version" on the context menu do? It seems to overwrite the installed version number with the latest online version number without actually updating the addon. If that's all it's supposed to do, may I suggest moving it to a different part of the context menu where it's not so easy to hit it by mistake?

    Also, trying to update Talented from Curse using "Update from local file" just hangs WUU. It says something like "1 addon queued for updating" and nothing else happens. Other Curse mods update from local file just fine. Nothing in the log file that I could see.
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    Just a suggestion for the F9 Open download pages feature: It should only open pages for the addons selected in the list.
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    Quote from Torhal
    I could see it being painful if you actually updated every addon manually. If you only updated the ones that actually required it, though...:D


    What I did was opened up WUU, used it to check which addons had new versions (at least that still worked at the time) and then opened up the addon pages from WUU for each one that I deemed a necessary upgrade. I think this was about 20 addons. 20 was painful enough, especially since for every one it's: click Download, click Manual Install, find original addon folder, delete it, extract zip. Throw in a recalcitrant extractor that wouldn't remember that I wanted to extract into the WoW addon folder and it gets really annoying.

    Anyway... All hail WUU, savior of RSI sufferers everywhere!
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    Quote from lejordet2
    The error would come on that version, yes; your current version of WUU is run to verify the new downloaded version, and that triggers the error - but next time it'll be better :)


    Ah, okay, I get it.

    Quote from lejordet2
    Some of the positioning code might be wonky - and/or might not make sense on Windows (WUU remembers its last position). I'll try without, and/or making an option to never remember.


    After I repositioned it the first time, it has been in the correct place every time I've started WUU since. So it looks like it was something related to the upgrade.

    Quote from lejordet2
    More stuff is coming to make the installations easier - the main priority now is to get the ideas out there and see what sticks :D


    I'm very grateful that you've made it possible to continue using WUU for Curse. The first day after the patch, I had to go update all my addons by hand. That was painful...
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    Using 633 on Vista 64...

    - Still got that error during the upgrade.
    - After upgrade, when I started WUU the window wasn't visible even though there was a button for it on the taskbar. I guessed that it was offscreen and was able to get it back onscreen by right-clicking the taskbar button and choosing Move.
    - Install from URL for Curse could do with a prompt to select the file. I managed to guess that I needed to use Update from file on the new entry in the addon list but not everybody will get that.
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    Quote from lejordet2
    That's not a critical error - it probably has updated just fine? I'll look at fixing it for later releases, though.


    Yeah, I noticed afterwards that it had actually updated. Oddly enough though, it didn't update until I tried the upgrade twice and then left it alone for a whole. Not sure what was happening there.
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    I just tried to get the 615 update through the app's auto update. During the install I get an error message popup which says to check the WUU.exe.log file. That file contains just this:

    C:\WUU\library.zip\Crypto\Hash\SHA.py:6: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
    C:\WUU\library.zip\Crypto\Hash\MD5.py:6: DeprecationWarning: the md5 module is deprecated; use hashlib instead
    C:\WUU\library.zip\Crypto\Hash\SHA.py:6: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
    C:\WUU\library.zip\Crypto\Hash\MD5.py:6: DeprecationWarning: the md5 module is deprecated; use hashlib instead
    C:\WUU\library.zip\Crypto\Hash\SHA.py:6: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
    C:\WUU\library.zip\Crypto\Hash\MD5.py:6: DeprecationWarning: the md5 module is deprecated; use hashlib instead


    Edit: Forgot to add, this is Windows Vista Home Premium 64-bit.
    Posted in: Updaters
  • 0

    posted a message on Loggerhead
    Any chance of getting an update to this to include Obsidian Sanctum and Vault of Archavon instances included? A ticket was filed for it over a month ago: http://www.wowace.com/projects/loggerhead/tickets/1-missing-instance-zones/
    Posted in: General AddOns
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    Quote from lejordet2
    Go to preferences and check "Preserve newlines as-is" - that happens on some computers, dunno why :(


    Well, it makes me suspect that when you're extracting files from the ZIP it's going through the text file mode conversion process. Double check that you're opening output files in the correct mode (e.g. open(file, "wb")). See http://docs.python.org/library/functions.html#open for more information.
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    I'm having a weird problem. Any addon that I have installed through WUU has had the line-endings screwed up in the files. They look like <CR><CR><LF>. This is confusing my text editor greatly. :(

    I double-checked that downloading the zip file from Curse directly didn't have the problem. And it seems to be happening to all addons installed by WUU, that I checked.
    Posted in: Updaters
  • 0

    posted a message on WoW UI Updater (Win/OSX/Linux, supports multiple sites), 1.6 thread
    Using latest version, I just got the following errors in the WUU.exe.log when I closed WUU. I had been cleaning up my addons list, deleting entries for addons that I had deleted directly from the folder some time ago, etc.

    Traceback (most recent call last):
      File "WUU.py", line 3887, in <module>
      File "WUU.py", line 3864, in bootWUU
      File "logging\__init__.pyc", line 1354, in shutdown
      File "logging\__init__.pyc", line 731, in flush
    ValueError: I/O operation on closed file
    Error in atexit._run_exitfuncs:
    Traceback (most recent call last):
      File "atexit.pyc", line 24, in _run_exitfuncs
      File "logging\__init__.pyc", line 1354, in shutdown
      File "logging\__init__.pyc", line 731, in flush
    ValueError: I/O operation on closed file
    Error in sys.exitfunc:
    Traceback (most recent call last):
      File "atexit.pyc", line 24, in _run_exitfuncs
      File "logging\__init__.pyc", line 1354, in shutdown
      File "logging\__init__.pyc", line 731, in flush
    ValueError: I/O operation on closed file
    Traceback (most recent call last):
      File "WUU.py", line 4020, in <module>
      File "WUU.py", line 3997, in bootWUU
      File "logging\__init__.pyc", line 1354, in shutdown
      File "logging\__init__.pyc", line 731, in flush
    ValueError: I/O operation on closed file
    Error in atexit._run_exitfuncs:
    Traceback (most recent call last):
      File "atexit.pyc", line 24, in _run_exitfuncs
      File "logging\__init__.pyc", line 1354, in shutdown
      File "logging\__init__.pyc", line 731, in flush
    ValueError: I/O operation on closed file
    Error in sys.exitfunc:
    Traceback (most recent call last):
      File "atexit.pyc", line 24, in _run_exitfuncs
      File "logging\__init__.pyc", line 1354, in shutdown
      File "logging\__init__.pyc", line 731, in flush
    ValueError: I/O operation on closed file
    Posted in: Updaters
  • 0

    posted a message on Recount
    No, but I have a full combatlog for that night, if you want.
    Posted in: General AddOns
  • 0

    posted a message on Recount
    I think I noticed a similar issue in BT last night. We only did 3 bosses but my memory use was up to ~70MB when it's normally ~30MB before a raid starts. I don't have any of the memory munching options turned on in Recount and normally it only goes up to about ~50MB for a raid night.
    Posted in: General AddOns
  • To post a comment, please or register a new account.