Getting a wierd error:
[03:18-126] Clique\libs\AceOO\AceOO-2.0.lua:644: FuBarPlugin-2.0: FuBarPlugin-2.0 requires Tablet-2.0.
*I only get this with Squishy enabled and it will radomly choose an addon that i have for this error, such as it has said "FruityLoots\libs\AceOO" "BigWigs\libs\AceOO" ect.
*Update: removed the FuBar, FuBar-2.0 deps from the .toc and core.lua and no problems now.
Oh. I didn't realize FuBarPlugin-2.0 requires Tablet-2.0 (which usually comes with FuBar2, so if you don't have FuBar2 installed you'll see that error). Guess I have to add another library to the libs/ folder. Can't access the SVN from where I'm now, so this might have to wait a bit.
scae, you can still configure Squishy via the slash options. The only thing that is going to change is that the header area won't open a dropdown anymore. If you have FuBar installed, you can choose to either have the menu in one of the bars or on the minimap, and if you don't have it installed, you'll have a minimap button you can move to wherever you want around the map.
[17:12-61]: Squishy\core.lua:691: Usage: UnitIsUnit("unit", "otherUnit")
<evaluated>: in function `UnitIsUnit'
Squishy\core.lua:691: in function `OnClick'
FuBarPlugin-2.0\FuBarPlugin-2.0.lua:607: in function <...Ons\BigWigs\Libs\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:605>
Fubar\FuBar.lua:1071: in function <Interface\AddOns\Fubar\FuBar.lua:1069>
- are you running FuBar, and if yes, is it FuBar 1.0, 1.2 or 2.0?
- did you click the icon on the minimap or in the FuBar itself?
I didn't manage to test the plugin a lot, but it worked for me using FuBar-2.0, both in the bar itself and also on the minimap. Also my plugin code is exactly 5 lines long (or short).
Maia, when I type /squishy alpha 0 the backdrop and border goes away as intended but the text "Squishy Emergency" is still there - anyway to toggle this off?
this is still on my to-do list.
teedog:
I tried this macro, but got the following error: [07:37-73]: Clique\Clique.lua:256: bad argument #1 to `find' (string expected, got nil) ...
unfortunately I can't reproduce any problems with Squishy:TargetSquishyUnitByPriority(). Please update Clique and check if it now works.
Grita, Samasnier, se7en:
I'd love it if all configuration was moved from the header to fubar or slashcommands
done.
c0rnflake:
Would it be possible to add a toggle to make that show up at the top of the frame instead of the bottom?
I can think of about 20 other toggles that would be nice too. At the moment I really don't see this as priority, and knowing that most addons died when they had too many options (because maintaining them gets more and more difficult), I don't really plan to do so.
Kyahx:
better icon
Do you like your new icon? What exactly is it, I don't get the reference. :)
Sarinthal, Rasapian:
Getting a wierd error:
[03:18-126] Clique\libs\AceOO\AceOO-2.0.lua:644: FuBarPlugin-2.0: FuBarPlugin-2.0 requires Tablet-2.0.
fixed.
scae:
Can I hid/disable the minimap/fubar icon? Edit: Maybe it would be cool to make the options a seperate/load on demand addon?
No - unless you use a program like Visor or MoveAnything to hide this specific frame. Also, a seperate addon for the options isn't viable.
Gamefaq, Iceroth:
When i click on the Fubar icon this pops up:[17:12-61]: Squishy\core.lua:691: Usage: UnitIsUnit("unit", "otherUnit")
I never tried left-clicking the icon when not having FuBar enabled. This is fixed now.
I am pleased to report that I spent an hour in AV on the PTR using the latest SVN and had no problems with the Roster getting out of sync, always was up to date, and never got stuck in whatever tight loop was killing my frame rate. Works like a charm.
I have all the wow icons decompressed and on the web, send me a PM if you're still looking for them. I'd rather not post the url because there's quite a few and I don't want it to become common knowledge.
Squishy\core.lua:545: attempt to index field `?' (a nil value)
Squishy\core.lua:545: in function `UpdateAggro'
Squishy\core.lua:475: in function `func'
Metrognome-2.0\Metrognome-2.0.lua:180: in function <...ddOns\BigWigs\Libs\Metrognome-2.0\Metrognome-2.0.lua:174>
/run local unit = Squishy:TargetSquishyUnitByPriority(1, 1); Clique:EfficientHeal(unit)
Obviously EfficientHeal could be substituted with EmergencyHeal if you wanted quicker casts :)
Still getting this error:
Clique\Clique.lua:256: bad argument #1 to `find' (string expected, got nil)
<evaluated>: in function `find'
Clique\Clique.lua:256: in function `CastSpell'
Plugins\Clique_HealSelect.lua:205: in function <...nterface\AddOns\Clique\Plugins\Clique_HealSelect.lua:159>
<unknown>:
<string>:"local unit = Squishy:TargetSquishyUnitByPri...":1: in main chunk
<evaluated>: in function `RunScript'
can you try
/script local...
instead of
/run local...
I wasnt using Clique, but I tried a /script print(Squishy:TargetSquishyUnitByPriority(1, 1)), which successfully printed stuff like "raid23" to my chat log - so I'm a bit clueless what the reason could be. Did you upgrade Clique yet? Does anyone else using Clique have that problem? Kyahx?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
[03:18-126] Clique\libs\AceOO\AceOO-2.0.lua:644: FuBarPlugin-2.0: FuBarPlugin-2.0 requires Tablet-2.0.
*I only get this with Squishy enabled and it will radomly choose an addon that i have for this error, such as it has said "FruityLoots\libs\AceOO" "BigWigs\libs\AceOO" ect.
*Update: removed the FuBar, FuBar-2.0 deps from the .toc and core.lua and no problems now.
Edit: Maybe it would be cool to make the options a seperate/load on demand addon?
[17:12-61]: Squishy\core.lua:691: Usage: UnitIsUnit("unit", "otherUnit")
<evaluated>: in function `UnitIsUnit'
Squishy\core.lua:691: in function `OnClick'
FuBarPlugin-2.0\FuBarPlugin-2.0.lua:607: in function <...Ons\BigWigs\Libs\FuBarPlugin-2.0\FuBarPlugin-2.0.lua:605>
Fubar\FuBar.lua:1071: in function <Interface\AddOns\Fubar\FuBar.lua:1069>
- are you running FuBar, and if yes, is it FuBar 1.0, 1.2 or 2.0?
- did you click the icon on the minimap or in the FuBar itself?
I didn't manage to test the plugin a lot, but it worked for me using FuBar-2.0, both in the bar itself and also on the minimap. Also my plugin code is exactly 5 lines long (or short).
Hmm.
AceOO\AceOO-2.0.lua:644: FubarPlugin-2.0: FubarPlugin-2.0 requires Tablet-2.0.
this is still on my to-do list.
teedog:
unfortunately I can't reproduce any problems with Squishy:TargetSquishyUnitByPriority(). Please update Clique and check if it now works.
Grita, Samasnier, se7en:
done.
c0rnflake:
I can think of about 20 other toggles that would be nice too. At the moment I really don't see this as priority, and knowing that most addons died when they had too many options (because maintaining them gets more and more difficult), I don't really plan to do so.
Kyahx:
Do you like your new icon? What exactly is it, I don't get the reference. :)
Sarinthal, Rasapian:
fixed.
scae:
No - unless you use a program like Visor or MoveAnything to hide this specific frame. Also, a seperate addon for the options isn't viable.
Gamefaq, Iceroth:
I never tried left-clicking the icon when not having FuBar enabled. This is fixed now.
gasp!
It's Kirby! How can you not know who Kirby is :(
http://en.wikipedia.org/wiki/Kirby_%28Nintendo%29
Allthou in retro-spect I like this image better (for an icon)
I have all the wow icons decompressed and on the web, send me a PM if you're still looking for them. I'd rather not post the url because there's quite a few and I don't want it to become common knowledge.
I have it enabled, but me kitty never showed up...
local PlayerHadAggro = roster[UnitName("player")].aggro
and the error indicates that you yourself aren't part of the raid/party. Which is pretty impossible. So I need details to track down the bug.
I don't know when it occured unfortunately. I just noticed 8 of that error in the logs after an hour or two in ZG.
Still getting this error:
can you try
/script local...
instead of
/run local...
I wasnt using Clique, but I tried a /script print(Squishy:TargetSquishyUnitByPriority(1, 1)), which successfully printed stuff like "raid23" to my chat log - so I'm a bit clueless what the reason could be. Did you upgrade Clique yet? Does anyone else using Clique have that problem? Kyahx?