The prat tbc version (should be latest one) makes me get an error when i try to do a macro...that x ui has caused something that is only allowed to be done by the blizzard ui. It refers to any ui though but it only happends if i have prat enabled.
just wondering if anyone has checked up on this? Sorry that i dont have any more info but i dont get any more error messages etc.
EDIT: I made the changes to the latest TBC build. They should fix this issue and the telltarget issue. If not, please let me know.
Appologies if this has been covered elsewhere, I've gotten used to having the PopupMessages and noticed that they've stopped working.
I checked the settings and noticed chat1 was set to OFF. I used "/prat popupmessage show chat1" to turn it to ON, but doing this casued me to stopped getting any chat at all.
Any ideas?
Thanks in advance.
Yeah, i commited with a testing flag on, sorry, its fixed in the current build.
it'd be handy to have a tool that tells you which stand alone libraries you need to download for the mods that you have, if you want to go that route. integrating it with WAU would be even better. ;)
You could see what was embedded and get the standalone versions of those. If it didnt have all its dependancies embedded, then it was an error or it should have required dependancies for the missing ones (because it doesnt support emvedded versions of them)
oh have nothing to do with, that I can't handle all the extra addons, it's when I add them to a InstallShield installer that I have the problems since I group the addons to enable users to choose which adds to use:
embeded libs triple the amount of files I need to add to the groups.
You wrote an installer, you should be able to manage the ace libraries with it and run standalone without any issues at all. I dont know why you would be using embedded libraries with an executable installer.
I figured I needed a project to start learning addon development... so here's a preview.
Things to do:
- Figure out how to turn a string into a function
- Make scroll frames for the addon list and options window
- Figure out a better layout for the options window
- Make the sliders and color select actually do something
- A bunch of little options that the ace options data table sometimes holds (like validation)
- Appearance options like color and size (right now it's nearly bigger than the screen at low resolutions)
- Fix it to work with the patch on Tuesday
- Get an SVN dev account and upload it
- Watch as the regulars cook up a new mod that does the same as this one in 15 lines of code.
It's been fun so far, though, and I hope to have a working version done by sometime next week.
Feel free to use either of the 2 mods i had modified as your base or just for code to copy or whatever ya need. Good luck, im excited to see what you come up with!
I think the current system is fine, as long as library authors stop breaking older addons (API changes) without updating the major version number.
API changes are not the most common case, though. More common is a mod will work with embedded librariex or !!!Libs, but not both, or installing it breaks another mod.
Ok, what about building a !!!StandaloneLibraries zip which contains the actual libraries instead of blanks, and have it triggered by chron, say - hourly?
You could even include script files like in my example.
It would mean that authors could depend on certain libraries being on the users machine. They could embed whatever other lesser used ones with thier addond.
Is that a step i0n the right direction? Are there some better ideas?
I don't want this to sound like a flame either but the Ace2 Library implementation is not the dll hell of windows, MS fixed dll hell by making dll have strong names and versions, I can now have 32 copies of foo.dll as long as they are all versioned and I will usually use the latest version. The problem here is that they are not all stored in one general place like the GAC so we have multiple copies everywhere and people are getting confused. The only time you should really have a problem is in cases like AceHook-2.0 which has had some of its features depricated in Lua and is now unusable for the most part (WoW 2.0) but there is an AceHook-2.1 so developers need to adjust their code to look for the new dll.
Actually, you arent arguing against what im saying at all - yes they did fix dll hell, but not really with the GAC this is a link if you are interested:
0
EDIT: I made the changes to the latest TBC build. They should fix this issue and the telltarget issue. If not, please let me know.
0
Yeah, i commited with a testing flag on, sorry, its fixed in the current build.
0
You could see what was embedded and get the standalone versions of those. If it didnt have all its dependancies embedded, then it was an error or it should have required dependancies for the missing ones (because it doesnt support emvedded versions of them)
0
You wrote an installer, you should be able to manage the ace libraries with it and run standalone without any issues at all. I dont know why you would be using embedded libraries with an executable installer.
0
If i have time after raid tonight ill do it. Cosmos did it - its 2-3 functions cut/paste.
0
Feel free to use either of the 2 mods i had modified as your base or just for code to copy or whatever ya need. Good luck, im excited to see what you come up with!
0
http://ui.worldofwar.net/ui.php?id=3310
or did you see the batch files i made?
0
Arent you supposed to be using the TBC branch on the PTR?
0
0
Yeah, i honestly never tried with items, probably need to set another attribute.
0
Read one page back
0
0
API changes are not the most common case, though. More common is a mod will work with embedded librariex or !!!Libs, but not both, or installing it breaks another mod.
0
You could even include script files like in my example.
It would mean that authors could depend on certain libraries being on the users machine. They could embed whatever other lesser used ones with thier addond.
Is that a step i0n the right direction? Are there some better ideas?
0
Actually, you arent arguing against what im saying at all - yes they did fix dll hell, but not really with the GAC this is a link if you are interested:
http://msdn2.microsoft.com/en-us/library/aa375193.aspx