| 03:27.11 | *** join/#riftuidev Noshei_ (~quassel@c-67-161-146-244.hsd1.co.comcast.net) |
| 07:20.15 | *** join/#riftuidev Baanano|afk (~chatzilla@202.pool85-59-204.dynamic.orange.es) |
| 08:18.50 | *** join/#riftuidev seebs (~seebs@home.seebs.net) |
| 08:18.51 | *** mode/#riftuidev [+o seebs] by ChanServ |
| 08:32.02 | *** join/#riftuidev seebs (~seebs@home.seebs.net) |
| 08:32.02 | *** mode/#riftuidev [+o seebs] by ChanServ |
| 09:02.08 | *** join/#riftuidev zz_Cidan (~cidan@2001:470:7:d8f::2) |
| 09:02.33 | *** join/#riftuidev Cidan (~cidan@conspiracy/developer/Cidan) |
| 09:17.57 | *** join/#riftuidev Noshei (~quassel@c-67-161-146-244.hsd1.co.comcast.net) |
| 09:23.13 | *** join/#riftuidev Wildtide|work (0fe3b94a@gateway/web/freenode/ip.15.227.185.74) |
| 12:20.39 | *** join/#riftuidev Wildtide|work (0fe3b94a@gateway/web/freenode/ip.15.227.185.74) |
| 12:28.57 | *** join/#riftuidev sylvanaar_work (~sylvanaar@pdpc/supporter/active/sylvanaar) |
| 12:51.15 | Wildtide|work | Nosh - I've just replied to your message on the forums with some thoughts on distance calculation |
| 15:23.18 | Noshei | yeah I saw your message and just sent my reply |
| 15:26.49 | Wildtide|work | nice one, looks good from a very quick look (stuck on the most boring conference call in history right now). i like the ordered pair idea, i'll have a go at adding it in |
| 15:27.12 | Noshei | gotta love conference calls |
| 15:27.25 | Wildtide|work | lol, if you're a masochist, yep :) |
| 15:27.31 | Noshei | lol |
| 15:31.29 | Noshei | not sure if you noticed, but I ended up using the distance squared instead of the actual distance |
| 15:31.53 | Noshei | saved having to do the square root and a couple % of cpu usage |
| 15:33.00 | Wildtide|work | that nil thing was a real pain actually. the SetPoint calls are really picky about which parameters you send in; i assume it's something to do with the interface between Lua and C++, but it was causing odd bugs that took ages to track down :) |
| 15:33.54 | Wildtide|work | i didn't notice, but that doesn't surprise me - that's the reason I separated the squared bit out, sqrt is a painfully expensive call |
| 15:34.10 | Noshei | I'm not sure if the ordered pairs was a newer update, but it is explained pretty well in the documentation now |
| 15:35.21 | Wildtide|work | it's always been there i think. i've used it occasionally, but left it out of the template stuff because i originally wanted end users to be able to write their own templates. i've given up on that idea though, as they will never be simple enough for non-coders to create |
| 15:36.00 | Wildtide|work | that didn't make much sense... but i wanted to keep the template table really simple. it didn't work out that way though :) |
| 15:37.04 | Noshei | I think you could still do that, but not in the sence that they actually edit the code, would have to be another gadget I would think |
| 15:37.48 | Noshei | so to test the ordered pairs I was using: point="TOPLEFT", element="frame", targetPoint=0, offsetX=1/3 in the template |
| 15:38.17 | Noshei | I also removed the , nil in element:SetPoint(attachPoint, attachToElement, attachTargetPoint, attachOffsetX, nil) |
| 15:39.09 | Wildtide|work | ah, gotcha |
| 15:40.52 | Noshei | and I guess you could do it as one field instead of 2 like I suggested in that pm |
| 15:40.57 | Wildtide|work | thinking the easiest way might be a simple anchor={x,y,z,a,b,c}, and pass the contents of the table straight into SetPoint using unpack(). that way you're just copying the SetPoint parameters into the template |
| 15:42.20 | Wildtide|work | i think that would work, and would be much less wordy than the current point=,targetPoint= etc |
| 15:43.16 | Wildtide|work | or possibly... setPoints = { {x,y,z}, {a,b,c}, {j,k,l,m,n,o} } |
| 15:43.22 | Noshei | yeah, would need a bit of documentation for it so if more people create templates they know how you have it set up |
| 15:44.09 | Wildtide|work | yep, sure would. i think that might be the way to go though. i'd have to leave the current method in for backwards compatibility as well, but i'll try adding it as another option |
| 15:44.59 | Noshei | still need to define the target frame though |
| 15:46.11 | Noshei | and I'm not sure if you can use an ordered pair for the attach point on the new frame, ill give that a try and see what happens |
| 15:46.20 | Wildtide|work | ah, yep. good point. in fact, i think that's what messed me up before when i had the same idea :( |
| 15:46.51 | Wildtide|work | you can. Zorba says somewhere that "TOPLEFT" is just another way of saying 0,0 |
| 15:55.10 | Noshei | I just always like to test stuff, never know where there might be a bug or typo. |
| 15:55.24 | Wildtide|work | true |
| 15:57.49 | Wildtide|work | though Zorba never makes typos or mistakes, he is a consummate professional and a flawless coder... |
| 15:58.22 | Wildtide|work | wonders if gratuitous fawning will give his wishlist priority :) |
| 16:03.02 | Noshei | lol |
| 16:03.26 | Noshei | now I just need to figure out a way to make text scale with the size of the frame |
| 16:08.53 | Wildtide|work | have a look at the vitality gadget, it was a load of painful handling of the built in resize events |
| 16:10.15 | Noshei | oh that reminds me, on the vitality gadget, when you hit 0% it changes from the red icon back to the normal grey one |
| 16:10.17 | Wildtide|work | i'm intending adding a couple of options to the Label element, to allow text to automatically scale with the height of a linked element, and also to have a parameter for the maximum length of text |
| 16:10.29 | Wildtide|work | does it? oops! |
| 16:11.04 | Wildtide|work | i don't think i've ever tested going that low. another one for the list |
| 16:12.27 | Wildtide|work | one of the problems i have with testing at the moment, is that my guild is dying, and i barely ever do anything except write my addon, which means things like that can easily go unnoticed :( |
| 16:13.57 | Noshei | ah, that sucks |
| 16:13.58 | Wildtide|work | i haven't really logged on properly since i got back yet, but from reading my guild forums, Blightweald (EU) is almost dead now. might have to re-home my characters |
| 16:15.21 | Wildtide|work | aye, it does. a lot of our players, including the GL and the other officers, are off to play GW2. i'll be in a guild of one at this rate :) |
| 16:19.26 | Noshei | just got another bug, though it may just be a pts issue, I died, then res'd at the graveyard, putting my vitality at 65%, but the gadget still shows 90% |
| 16:20.51 | Noshei | yeah it seems that it isn't updating the vality text unless there is a ui reload, like when I release and port back to the graveyard |
| 16:40.51 | Wildtide|work | oh, that's odd. though 65% vitality looks like a RIFT bug as well - it's impossible to have 65% |
| 16:43.18 | Wildtide|work | if you get chance before i do, can you run "/eventlog Vitality" and just check whether or not the game is sending us sensible events? the text not updating should mean we're not getting the update event |
| 16:44.28 | Wildtide|work | time for me to head home, hopefully catch you later if the missus doesn't have me putting up furniture all evening ;) |
| 17:13.24 | Noshei | hey ZorbaGama, did anythinc change with Event.Unit.Available on the PTS? I know it's deprecated, but it doesn't seem to be firing correctly now |
| 17:13.50 | Baanano | hi |
| 19:25.35 | *** join/#riftuidev Noshei_ (~quassel@c-67-161-146-244.hsd1.co.comcast.net) |
| 19:28.09 | *** part/#riftuidev Noshei_ (~quassel@c-67-161-146-244.hsd1.co.comcast.net) |
| 19:28.11 | *** join/#riftuidev Noshei_ (~quassel@c-67-161-146-244.hsd1.co.comcast.net) |
| 19:37.02 | *** join/#riftuidev Cairenn (~Owner@MMOI/Administratrix/Cairenn) |
| 19:37.03 | *** mode/#riftuidev [+o Cairenn] by ChanServ |
| 20:56.40 | *** join/#riftuidev Torhal|work (~torhal_wo@67.58.77.206) |
| 20:56.41 | *** mode/#riftuidev [+v Torhal|work] by ChanServ |
| 21:21.19 | ZorbaGama | noshie, there's been a bug or two. if you can give repro steps I can look into it |
| 21:38.33 | ZorbaGama | while I technically said "Event.Unit.Unavailable is keeping its current behavior", note that the "current behavior" had to be pretty much reimplemented from scratch, so it wouldn't surprise me at all if it differs :P |
| 21:38.43 | ZorbaGama | Although there should be a patch coming up shortly. |
| 21:57.33 | Noshei_ | ok, I was just wondering because I was seeing some odd behavior, and switching to Event.Unit.Availability cleared it up |