is it possible to make a mod that shows in one frame, every piece of loot on the mob?
instead of opening a mob and having 2-3 pages of loot, or even chests with sometimes 2-4 pages, would it be possible to have one big long frame, or even a double-wide frame to see everything at once?
gonna copy this over to the AceLoot topic too. maybe it's a small & easy thing to add in to the options.
Need to be placed in INTERFACE/FrameXML folder to function.
1.10 you can't put anything in the FrameXML.. if there isn't a programatic way to do this we need to let slouken know so he can give us that functionality.
There is going to be a proverbial assload of possibilities with fonts in the game in 1.10. You will be able to change every font in the game on the fly with a small amount of LUA.. Iriel's already written a small afunction to handle most of it =).
I'm hard over 1.10 if you couldn't tell. What we REALLY REALLY need to do is have a whiteboard app that uses CTRA or some channel to communicate.. Dynamic frame creation made it possible.. we just need to buck up and code it.
Have to find new ways to destroy the blizzard UI Then.
I want FrameXML hacks because that is the most efficient way to destroy the blizzard frames, instead of using some addon or multiple to remove this and that window after they are loaded and created in the game.
Please ask Slouken to reconsider the ban, or at least give any sane reason for not allowing people to modify the xml elements the game uses.
Because its always been a bad idea, it gives hell for anyone who does mod development trrying to support their users, and everything should be possible through LUA scripting exclusively.
I want FrameXML hacks because that is the most efficient way to destroy the blizzard frames, instead of using some addon or multiple to remove this and that window after they are loaded and created in the game.
How is destoying a frame in wow easier through FrameXML than in LUA. If you want to destroy a frame.. unregister its events and kill it..
Please ask Slouken to reconsider the ban, or at least give any sane reason for not allowing people to modify the xml elements the game uses.
Its not a ban.. and the reasons are completely sane and reasonable. FrameXML may work for you to do the 0.1% of things that you need to do.. but they're a nightmare overall.. He announced this TWO patches ago, and asked over and over again for functionality that he'd need to add to the LUA environment to compensate for the loss of FrameXML overrides.
We've gotten so many presents since then.. its insane. 1.10 is a huge step.
Because its always been a bad idea, it gives hell for anyone who does mod development trrying to support their users, and everything should be possible through LUA scripting exclusively.
Everything SHOULD be possible through LUA, but it is not.
Unless you can show me a way to STOP WoW.exe from loading PlayerFrame.xml/lua, TargetFrame.xml/lua, RaidFrame.xml/lua, PartyFrame.xml/lua.
It does not give hell to anyone making mods to support their users, unless their users are of such a nature as they would have trouble doing most things on the computer, in which case I think the Blizzard Default UI is the best for them.
Perhaps offering the addon as a password protected file, requiring the user to type "CONFIRM" to even extract it, would be enough to discourage the masses from using it.
Of course, regardless, people will download it, then blizzard will patch, and they will complain on the Blizzard Tech Forums that nothing is working, and the culprit will be an addon the user did not update. Thus a workaround would be for a user to connect ' to the tech forums trough an application they launch from the wow folder that backups their settings, launches the game, ask if everything is ok, and then tell them what has happened. - That would of course lead to complains that "BLIZZARD RUINED MY UI (Which was already broken, since I ran the utility, but lets not mention that, since its blizzards fault)... )
How is destoying a frame in wow easier through FrameXML than in LUA. If you want to destroy a frame.. unregister its events and kill it..
Most efficient, not easier.
When WoW Launches, it reads the .mpq files as well as the Interface folder.
If it finds something in the Interface/FrameXML folder, this will REPLACE the files from the patch.mpq/Interfaces/FrameXML folder.
The result is that - only ONE version of the file is loaded - MINE.
And my file is 20bytes, whereas the blizzard one, in addition to containing a LOT of functions, onupdates and whatnot, is around 15KB per xml/lua replaced.
Every other method of destroying frames and functions is inferior to a frameXML replacement.
Its not a ban.. and the reasons are completely sane and reasonable. FrameXML may work for you to do the 0.1% of things that you need to do.. but they're a nightmare overall.. He announced this TWO patches ago, and asked over and over again for functionality that he'd need to add to the LUA environment to compensate for the loss of FrameXML overrides.
We've gotten so many presents since then.. its insane. 1.10 is a huge step.
He may have asked, but as I am a European player I have NO ACCESS to the US Forums.
And How are they are nightmare, except for when USERS dont stick with the programme, which they do not do anyway so regardless they WILL get support incidents because of USERS. If they wanted to stop USERS from reporting stupid mistakes, they would have to disallow ANY modification of the game UI. FrameXML is just the start I suspect, and eventually there will be no addons or only Blizzard Sanctioned ones.
So to repeat myself: THOSE BASTARDS.
Because they ruin functionality that I want, Need, Use, Can Cope With.
I've uedrameXML for some imple repllacement. I'm not sure why we dont oust AddOns in Favors of FrameXML, then again, that's not friend;y except for the developer. FrameXML is awsome, I agree with instant, those bastards.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
instead of opening a mob and having 2-3 pages of loot, or even chests with sometimes 2-4 pages, would it be possible to have one big long frame, or even a double-wide frame to see everything at once?
gonna copy this over to the AceLoot topic too. maybe it's a small & easy thing to add in to the options.
thanks!
--- Edit ---
Looking at the FrameXML, you'd have to replicate the following element up to 'x' however many max buttons you want available.
That and the above should do it.
now...where should i put that? (no smart comments pls!) haha
and it looks like it would have to be a static-length frame?
i was hoping it would be possible to have a 4-slot frame if the mob had 4 loots on him. or 12 slot frame if he had 12 loots.
i haven't done much master looter stuff either. wonder how that would work.
thanks for the replies ;)
-
View User Profile
-
View Posts
-
Send Message
Curse Premium6 slot loot window dirtydirty hack.
Need to be placed in INTERFACE/FrameXML folder to function.
1.10 you can't put anything in the FrameXML.. if there isn't a programatic way to do this we need to let slouken know so he can give us that functionality.
hope clearfont author updates his stuff!
There is going to be a proverbial assload of possibilities with fonts in the game in 1.10. You will be able to change every font in the game on the fly with a small amount of LUA.. Iriel's already written a small afunction to handle most of it =).
I'm hard over 1.10 if you couldn't tell. What we REALLY REALLY need to do is have a whiteboard app that uses CTRA or some channel to communicate.. Dynamic frame creation made it possible.. we just need to buck up and code it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThose bastards
Do they give any explanation why?
Argh.
Have to find new ways to destroy the blizzard UI Then.
I want FrameXML hacks because that is the most efficient way to destroy the blizzard frames, instead of using some addon or multiple to remove this and that window after they are loaded and created in the game.
Please ask Slouken to reconsider the ban, or at least give any sane reason for not allowing people to modify the xml elements the game uses.
.. argh, those bastards.
Because its always been a bad idea, it gives hell for anyone who does mod development trrying to support their users, and everything should be possible through LUA scripting exclusively.
How is destoying a frame in wow easier through FrameXML than in LUA. If you want to destroy a frame.. unregister its events and kill it..
Its not a ban.. and the reasons are completely sane and reasonable. FrameXML may work for you to do the 0.1% of things that you need to do.. but they're a nightmare overall.. He announced this TWO patches ago, and asked over and over again for functionality that he'd need to add to the LUA environment to compensate for the loss of FrameXML overrides.
We've gotten so many presents since then.. its insane. 1.10 is a huge step.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumEverything SHOULD be possible through LUA, but it is not.
Unless you can show me a way to STOP WoW.exe from loading PlayerFrame.xml/lua, TargetFrame.xml/lua, RaidFrame.xml/lua, PartyFrame.xml/lua.
It does not give hell to anyone making mods to support their users, unless their users are of such a nature as they would have trouble doing most things on the computer, in which case I think the Blizzard Default UI is the best for them.
Perhaps offering the addon as a password protected file, requiring the user to type "CONFIRM" to even extract it, would be enough to discourage the masses from using it.
Of course, regardless, people will download it, then blizzard will patch, and they will complain on the Blizzard Tech Forums that nothing is working, and the culprit will be an addon the user did not update. Thus a workaround would be for a user to connect ' to the tech forums trough an application they launch from the wow folder that backups their settings, launches the game, ask if everything is ok, and then tell them what has happened. - That would of course lead to complains that "BLIZZARD RUINED MY UI (Which was already broken, since I ran the utility, but lets not mention that, since its blizzards fault)... )
Most efficient, not easier.
When WoW Launches, it reads the .mpq files as well as the Interface folder.
If it finds something in the Interface/FrameXML folder, this will REPLACE the files from the patch.mpq/Interfaces/FrameXML folder.
The result is that - only ONE version of the file is loaded - MINE.
And my file is 20bytes, whereas the blizzard one, in addition to containing a LOT of functions, onupdates and whatnot, is around 15KB per xml/lua replaced.
Every other method of destroying frames and functions is inferior to a frameXML replacement.
He may have asked, but as I am a European player I have NO ACCESS to the US Forums.
And How are they are nightmare, except for when USERS dont stick with the programme, which they do not do anyway so regardless they WILL get support incidents because of USERS. If they wanted to stop USERS from reporting stupid mistakes, they would have to disallow ANY modification of the game UI. FrameXML is just the start I suspect, and eventually there will be no addons or only Blizzard Sanctioned ones.
So to repeat myself: THOSE BASTARDS.
Because they ruin functionality that I want, Need, Use, Can Cope With.
/sadface