If you really have some spare time and are able to code lua, take the Squishy priority code and write a module for Grid - to e.g. highlight the three units that need a heal more than anyone else. How 'bout that? :)
then have a look down the very bottom left corner of the screen, that's where it was for me xD
Yeah, sorry, I didnt realized it's defaulting to that corner, and probably is even behind the blizzard action bar, so you won't see it at all. Hope I don't forget to change this (add a "or 500" to both x and y variable in :RestorePosition() )
I noticed using this addon ( correct me if i'm wrong ) that the party members got priority over the rest of the raid, can i disable this feature?
You can't - unless you edit the code. Search for the line:
if not isInBattleground and UnitInParty(u.unitid) then m = m - math.max(20, GetNumRaidMembers()) end
and just delete it completely.
Is this addon working at all? Downloaded last version (Squishy-r14640.zip and two older) and tried to run wow, all I get is error about AceTab-2.0.lua:268: Attempt to call method 'HookScript' (a nil value).
Well, some new libraries were released (all the 2.1 and 2.2 stuff you're seeing out there), and for some reason people decided to upgrade all addons to the new libraries without checking if it breaks anything or not. I havent dared to update my svn since that happened (about 10 days ago), as when I noticed how many people had problems I simply decided to wait for a few more weeks instead.
So what happened is that someone replaced the AceHook-2.0 by AceHook-2.1 in the Squishy embedded libraries - without noticing that AceTab still requires AceHook-2.0. So either someone upgrades AceTab to use 2.1 (therefor likely breaking other addons), or I'll add both AceHooks to Squishy, or I'll simply revert to the old version. Btw, you won't notice that problem if you have any other addon installed that has AceHook-2.0 as embedded library, as Squishy will simply take it from there.
If someone else wants to take care of the problem, please do so. Or get revision 14227, which is the last one that works without problems.
One strange thing I notice is if I have my main tank targetted(so I can quick heal him if needed), and I use the macro, sometimes it will change my target to who I'm currently healing
Hmm, no idea what's going on there, but honestly: I don't plan to find a fix for it, as this functionality won't work in TBC.
One simple request to an already wondeful addon, would it be possible to have it toggle on only in raids also? While in 5man groups its nice to see and all but most of the not nessecary to me at least. Keeping it hidden until a raid is formed would be very helpful.
I'm not planning to spend any more time on the Squishy code, but I recommend looking at the function CheckVisibility(), I bet you'll be able to easily alter it to only show it in raids.
Can you update Squishy for the lastest CastParty, so I don't need to update it everytime.
As I won't be updating Squishy anymore, you won't need to update it anymore too ;) But this has been asked for like a month ago, and a month ago my reply was: "please provide the hooking code that won't break the old versions of CastParty so I can add it", and I havent heard anything since. I don't really want to make a change that breaks compatibility with older versions of an addon.
As for the french translation: why don't you just grab the english locals file, compare it with the old french file to see what was added and what was changed, make the necessary changes, test them a bit and then commit them to the SVN? I can't really help you much there as I have no french client I could test Squishy with.
Maia, with the changes coming to TBC, where supposedly you won't be able to do emergency monitors, I'm worried that my beloved Squishy won't survive. Have you heard anything about it?
From what I can tell, Squishy will be dead (like ANY other emergency monitor or unit frame addon that dynamically shows/hides units). Detox will be dead too (not only the keybinding, also click-casting onto units in the tooltip).
Blizzard tried to kill "smart buttons". They killed "smart displays" too.
The problem is the TargetUnit(unit) at the end of the OnClick function. In the latest revisions it looks misplaced or unnecessary as it is always executed and not conditional. I commented it out, and it works again.
The latest revision is now exactly using the PerfectRaid OnClick() code, so everything should work fine again.
Though this is sort of a "kitchen sink" approach, can variable class/group roster limitations be an expected feature in the future?
Actually I was planning to implement it myself, plus two other people seem to have coded it already. I havent seen their code yet though.
you need to remove : ["Blizzard"] = "Blizzard",
actually the french local file needs more than that, as all the new options I added recently aren't translated yet.
As for the recent change in the click targetting code: I'll probably revert my code as its causing more problems than its helping. If someone sees Cladhaire in the IRC, you might want to ask how it should be.
As for the FloatingChatFrame.lua error: this is caused by a recent version of AceComm (which Squishy is using, as other addons are using it too), and there's nothing I can do to fix it, other than keep bugging ckknight (the author of AceComm) to finally fix it somehow (bug him if you see him in IRC). Sorry...
r13003: many new frame display options: show/hide border, show/hide header, bar width, bar height, bar coloring by class or ctra style. I'm not done yet, more to come in the next few days.
sorry if i missed it, but i believe something has changed with one of the recent squishy versions when it comes to click casting. i use clique with squishy, and i'm using squishy r12904. i'm not positive, but it might of been the OnClick() change.
Hmm, there was a tiny change, but I assumed that what Talyn posted doesnt break anything. The return statement has slightly changed, but I hope someone can take care of it (I never click cast and don't use any of the addons myself).
FYI: I'm rewriting the entire frame code to have it as similar to the eeMon code as only possible. Why? Two reasons: it'll reduce the work Evil and I both have on frame code, and also it'll allow me to slowly add all the options eeMon has.
EDIT: hit 'post' too early. If you're seeing problems with the frame display or any options, please let me know. I try hard not introducing new bugs, but it can always happen.
If you're getting an ERROR message, you're definetly not using the latest version, as the latest version will try to ignore the problem and only print some debug code if you have it enabled.
To explain what's happening behind (and maybe someone wants to look at the code):
Squishy:UpdatePriority() is called several times a second. It will loop through all units in the group and set their priority (.pri) to a number (either 1000 if we want to ignore them, as out of range, full health,...), or to something between 0 and 200ish. It will then sort the table by that value, to then display the 10 units with the highest (err, lowest number) priority. The error you're seeing is that for some reason .pri can nil for pets - which is pretty impossible, as I'm setting it to 1000 for all units.
I'm only seeing the problem when a damaged pet is around me, and it'll spam debug a few times (btw, it should only print the debug once, as it should fix itself), and then work again. It's not like pet support generally isnt working at all.
And as I havent changed anything related to this code in the last months I'm clueless what's going on.