• 0

    posted a message on AceComm-2.0 Error
    After a little checking of the mod Bongos Skinned Map which was reported to be breaking Threat-1.0 for unknown reasons, I found that version 5.1 was setting MiniMapBattlefieldFrame.status = "active" but version 6 and latter weren't. So that untraceable bug was caused by this one.
    Posted in: Libraries
  • 0

    posted a message on AceComm-2.0 Error
    http://www.lua.org/manual/5.1/manual.html#pdf-string.char

    Note that numerical codes are not necessarily portable across platforms.


    Stan_ on IRC mentioned getting this error and when I asked he said he was using Vista with everything set to German and WoW in enGB. But as we all should know, Lua isn't unicode and WoW translations are just locale files so his WoW is still running on a German codepage. I'm willing to bet that somehow this is related because I have never gotten this error and nobody in my guild has ever mentioned getting this error and we're all American or Canadian (a few French Canadians but I have no clue what locale their Windows is in).

    Has anybody who's gotten this error mentioned what codepage is being used for non-unicode programs on their computer? I think it would be a good idea to start asking and if somebody answers "English (United States)" then we'll know this probably isn't related to codepages.

    EDIT: Stan_ tested "t={} for i = 1, 255 do table.insert(t, i) end return string.char(unpack(t))" and no error so probably safe to disregard my wild theory.

    EDIT2: "312 [306] SETGLOBAL 99 -135 ; EncodeBytes" in AceComm-2.0.lua, fix please then slap ckknight and figure out wtf these are suppost to be....
    "451 [1062] GETGLOBAL 12 -35 ; finish"
    "468 [1066] GETGLOBAL 13 -35 ; finish"
    Posted in: Libraries
  • 0

    posted a message on Tiny Tip replacement ideas
    Update? Works fine for me.
    Posted in: General AddOns
  • 0

    posted a message on ImprovedRaidWarningFrame
    Yes its abandoned, and its going to need a complete rewrite anyway due to the major change to the RaidWarningFrame in 2.3.
    Posted in: General AddOns
  • 0

    posted a message on EQCompare vs Mirror/tekKompare
    Quote from Elsia »
    Why is translation on an otherwise not updated addon not OK? I see there is honest-to-good german translation as recent as Nov 11 2007. There are a number of addons whose main recent feature is that they get more translation. Why do you single EQCompare out?


    Thats not what I said. Every toc bump after 20000 done to EQCompare was done by a translator not an addon developer (revering to any addon developer not just a developer of EQCompare) so they shouldn't have been done in the first place. The toc bump to 20000 was done by an addon developer but the code wasn't fixed for 2.x (again refering to the macro tainting issue that caused sooo many forum posts when nobody could figure out what was doing it and other issues).

    I was under the impression that addons without toc's above 20000 wouldn't appear on files.wowace and thus wouldn't make it into the xml feed to show up on WAU, I guess I was incorrect about that and didn't know since I don't use WAU or any other updater that uses the xml feed.
    Posted in: General AddOns
  • 0

    posted a message on EQCompare vs Mirror/tekKompare
    The reason I put the toc at 11200 instead of 20003 was so that it wouldn't showup in WAU or on files.wowace.com so new users wouldn't see it and install it. I was actually trying to move it from trunk to tags on the svn then see about getting somebody to just delete it from files.wowace.com so that it would still be around if somebody wanted to pick it up in the future and move it back to trunk and it wouldn't show on files.wowace.com. But I ran into a snag and kept getting 400 Bad request errors from the svn when trying to svn move it. The current 20003 toc is fine now I guess as long as people don't bump it again but it's mostly been the translators that keep bumping the toc.
    Posted in: General AddOns
  • 0

    posted a message on Install ..
    If it says that "Cartographer" is missing a dependency on the addon screen then you must have tried to install "Cartographer1" then removed it. Delete Cartographer folder and reinstall Cartographer.
    Posted in: Map/Minimap AddOns
  • 0

    posted a message on Quartz: Modular Casting Bar
    The latency feature actually does that stuff with lots of non spell casts.
    Posted in: General AddOns
  • 0

    posted a message on EQCompare: mod for QuickCompare/EquipCompare replacement.
    Mirror still seems inferior to tekKompare to me code wise though.

    And the EQCompare toc is not getting fixed!

    EDIT: You know what nevermind, I will fix the toc.
    Posted in: General AddOns
  • 0

    posted a message on Same error EVERY install of cartographer
    Fixed.
    Posted in: Map/Minimap AddOns
  • 0

    posted a message on Some errors fixed still have some errors.
    Download from files.wowace.com NOT from ui.worldofwar.net because nobody ever uploads new versions to that shitty site.
    Posted in: Map/Minimap AddOns
  • 0

    posted a message on Improved Raid Warning Frame
    It needs a complete rewrite instead of an update.
    Posted in: General AddOns
  • 0

    posted a message on EQCompare: mod for QuickCompare/EquipCompare replacement.
    Yeah even EquipCompare which was the addon EQCompare was originally written to replace has gotten updated and become much much better than EQCompare because it actually gets updated. EQCompare is dead, if you want the lightwight replacement without configuration that uses the blizzard compare tooltips get tekKompare, if you want the heavier replacement with more options that replaces the blizzard tooltips (like EQCompare does) get EquipCompare.

    tekKompare: http://www.wowinterface.com/downloads/info6837-tekKompare.html
    EquipCompare: http://www.wowinterface.com/downloads/info4392-EquipCompare.html http://wow.curse.com/downloads/details/166/
    Posted in: General AddOns
  • 0

    posted a message on EQCompare: mod for QuickCompare/EquipCompare replacement.
    Quote from tekkub »

    Ranged as in the gun slot, or the ammo slot?


    Gun slot, EQC sets a bunch of the INV_* global vars that used to be nil (I think they might be set now I'm not sure) so that it can getglobal() the strings returned by GetItemInfo() to figure out that all the different ones used by the ranged slot are the same. This was actually the cause of all the "Ace2 has been blocked from preforming a protected action" messages from using [equiped] in macros when TBC first came out because one of the C functions used by that option actually reads all those INV_* global vars. I moved all the 6 or so locale files for EQC into the main addon file so I could make that a local change instead of global to fix that. But it still had lots of issues back then before I switched to tekKompare and the only commit since then other than localizations was something specific to the atlasloot tooltips so nothing has been fixed.

    Tell the Examiner author to fix his code so tekKompare works with it because hes obviously the one doing something different than every other author so theres no way in hell tekKompare will get code to work on his tooltips.
    Posted in: General AddOns
  • 0

    posted a message on EQCompare: mod for QuickCompare/EquipCompare replacement.
    Also I'm pretty sure the ranged slot comparison in EQCompare is somewhat broken due to my fix a long time ago to prevent it from tainting and completely breaking some macro functions. And the size difference between EQCompare and tekKcompare doesn't have anything to do with features, its all about EQCompare being written for WoW 1.x and not using functions available by the default ui making it have to do all the calculations on what slot an item should be compared against and frankly very poor design of doing that because of the workarounds needed in WoW 1.x due to api inconsistances.
    Posted in: General AddOns
  • To post a comment, please or register a new account.