Having issues with the current SVN version. Roster seems to be getting out of sink, but I'm having trouble debugging it. I assume it's caused by the pet support, but when I tested it with a single pet, it worked fine. *boggle*
Latest SVN version, I can't even get Squishy to show the frame.
Hrm. You did enable solo mode, or were grouped at that point? If yes, did that only happen after enabling pet support?
I was in a raid and never got the thing to show after trying to toggle both solo and pet support. It did load up as soon as I left the raid and worked as solo, then still showed up while I was in a party.
Sorry for the issues when in a raid. Adding pet support seem to have broken the roster functions. I just updated Squishy to 1.11 and fixed the roster troubles related to pets and raids, and even though I didn't run a 40man raid yet at least Squishy does work for my lvl11 hunter in a party and also for my main toon in a 10man raid.
I'm unsure if raid pets show up in the emergency monitor though, at least your own pet will show.
Furiouso, may I ask which click-casting mod you're using? Also, does the error always happen, or only when clicking on specific units? Does it happen in parties and/or raids? The error you're seeing is indicating that the unit you clicked on doesn't have a unitid (which is something like "player", "pet", "party2", "raid36",...). I can add a line to simply ignore such situations, but I'd prefer to find out why this problem happenes.
Teedog, that's an interesting bug too (and I'm sorry the latest Squishy versions are causing so many problems - I really hope I can fix them all soon). The options.lua:197 error indicates that for some reason the emergency frame (aka the thing with the black background and the border) hasn't been created properly. Unfortunately I cannot reproduce this problem, the frame shows for me no matter what I do (besides the raid related pet bugs that occur sometimes).
Now interestingly this frame is created when the addon is enabled (aka right after logging in), and theoretically nothing should try to access the frame before it's enabled. Actually there is a *tiny* chance that the event that tries to access the frame fires a fraction of a second before the frame is created itself, but then this might only happen in 1 of 1000 logins. Does it always happen for you? Does it only happen on login? Does it work properly if you do a '/console reloadui'? Or a '/ace disable Squishy' followed by a '/ace enable Squishy'? Were you in a party or raid at that time? Did you turn on the frame lock?
I'm trying my best to fix these problems (which might also be related to 1.11 and a new order of events firing), so there more information you can give the easier it will be.
Does it always happen for you? Does it only happen on login? Does it work properly if you do a '/console reloadui'? Or a '/ace disable Squishy' followed by a '/ace enable Squishy'? Were you in a party or raid at that time? Did you turn on the frame lock?
Yep it always happens to me. I have not been able to see Squishy since 1.11.
/console reloadui doesn't help. I can't see Squishy upon login, nor can I see it after a /rl.
I tried '/ace disable Squishy' followed by a '/ace enable Squishy' to no effect. Same error when running any /sq config command, still can't see Squishy.
I've tried it in a raid or solo, with solo mode both on and off.
Firiel, teedog, I'm sorry to hear you're still having these problems. While I'm somewhat busy these days and might not be able to fix anything before sunday (maybe tomorrow though), I'd like to ask you to either revert to a SVN version pre-pet-support (as these should be working), and/or try to find out why these problems happen at all (stupid question: you didnt hide the backdrop, did you?).
As Squishy works for me on the 1.11 US client with and without my pet, when soloing, partying and raiding, I guess the next step is to add debug code to a slash command that will print what's going on, and then ask you to report back what it's saying so I can narrow down the problem.
I've found pet support to be buggy. My understanding based on what Maia has told me is that if you don't have a pet out yourself, the raid roster gets confused and hides the frame to build a new roster on the next update. Since you still don't have a pet then, the frame stays perpetually hidden (hence why slash commands work) becuase the roster is always "wrong". This bug is not yet fixed to-my-knowlage.
Try turning pet support off, then doing a /console ReloadUI - newest version from the SVN runs fine for me with pet support turned off.
as for the buggy pet support. I just spent another hour testing it. Everything worked fine. No matter if soloing, in party or raid, no matter if with or without pet support, no matter if me or others had pets summoned.
But: I updated the SVN. New option: "/squishy WTF". Please use it if you're experiencing problems. It won't fix them, but it will tell you in the chatframe why Squishy thinks its roster data is incorrect. This can be something like:
roster incomplete, hiding Squishy frame <-- you'll see that when you're having problems
count mismatch: roster:3 members:6 <-- 3 units in the Squishy roster, but it should be 6.
Steve (raid23) not in roster. <-- for some reason we can't add Steve.
Steve in roster but should be deleted. <-- you were grouped with Steve, but he left.
Finally: in general it seems that if an addon has a 'hard' error wow will auto-disable it. In that case you might have to "/console reloadui" to reload the user interface (takes 2-5sec), e.g. if you're having issues with pet support and want to revert to a working squishy without pet support.
Grita, now that's very strage. I now added some more code to the WTF option. It will now also tell you if for some reason the frame is hidden, if the backdrop is shown or not, it will display the x and y coordinates of the frame (maybe it was moved off screen?) and then reset all options to the defaults and move the frame to the center of the screen.
Please tell me if that helps, and what it says. Thanks.