| 00:41.05 | *** join/#riftuidev Noshei (~quassel@c-67-161-146-244.hsd1.co.comcast.net) |
| 01:55.11 | *** join/#riftuidev arton (~arton@63.142.161.8) |
| 05:31.57 | Thorarin | *sigh* still getting performance warnings in places that make no sense at all :( |
| 05:33.11 | Thorarin | Code is checking for remaining time constantly, barely anything happens in between |
| 05:35.42 | *** join/#riftuidev Imhothar (miranda@host-188-174-167-211.customer.m-online.net) |
| 08:01.15 | Noshei | ZorbaTHut: when do you think we should be able to start working with the guild api on PTS? |
| 08:22.34 | *** join/#riftuidev NuSuey (u3556@gateway/web/irccloud.com/x-rfkatolrkabyszlx) |
| 08:25.25 | *** join/#riftuidev Torhal (~torhal@c-71-207-224-241.hsd1.al.comcast.net) |
| 08:25.26 | *** mode/#riftuidev [+v Torhal] by ChanServ |
| 11:14.44 | *** join/#riftuidev KaeltenAway (~Kaelten@WoWUIDev/WoWAce/WoWIFA/CurseStaff/kaelten) |
| 11:14.44 | *** mode/#riftuidev [+o KaeltenAway] by ChanServ |
| 11:36.46 | ZorbaTHut | noshei, you can start working with it now if you want - I think about 95% of it isn't planned to change - but the broken error report system is probably going to make your life difficult |
| 11:37.26 | Noshei | lol, yeah I noticed a few issues there. I like the little addition you added to the error window though |
| 11:37.50 | Noshei | +1 for great english |
| 11:38.06 | ZorbaTHut | which one? I think there were a few tweaks to the error window |
| 11:38.32 | Noshei | was a button, something about allowing an addon to work |
| 11:38.46 | ZorbaTHut | oh, there's a Compatibility Mode Enable button |
| 11:38.52 | Noshei | yeah that |
| 11:39.00 | ZorbaTHut | but note that that button will go away again shortly, so make sure your addon doesn't rely on it :V |
| 11:39.26 | Noshei | what is it there for? |
| 11:39.54 | ZorbaTHut | you know how I've been saying "x is deprecated, stop using it"? in the next major version, trying to use X will cause an error, unless the user explicitly goes into compatibility mode |
| 11:40.01 | ZorbaTHut | in the version *after* that, compatibility mode goes away. |
| 11:40.36 | ZorbaTHut | check out http://forums.riftgame.com/rift-general-discussions/addon-api-development/258721-upcoming-breaking-changes.html for more info and a list of how all functionality can be accomplished without the deprecated functions |
| 11:40.55 | ZorbaTHut | you can also test it now on live by adding Command.System.Strict() to the first line of your first file (remember to remove it before you deploy a new version though) |
| 11:41.03 | Noshei | oh yeah I'm good, I make sure not to use deprecated functions |
| 11:41.45 | ZorbaTHut | note that the "compatibility mode enable" button will show up on the error report only if it detects a deprecated function or event being used :) |
| 11:41.53 | Noshei | yeah I figured thats what it was for, just wasn't sure |
| 11:41.57 | Noshei | ah nice |
| 11:42.22 | Noshei | so the version after the next, likely to be storm legion? |
| 11:43.00 | Noshei | i remember someone saying there wont be a 1.11 |
| 11:43.14 | Noshei | was on one of the live streams I think |
| 11:43.53 | ZorbaTHut | I'm not gonna get into details, but our standard version release pattern is changing a bit until storm legion is out. Things will be a little hectic. |
| 11:43.55 | ZorbaTHut | And, honestly, when I say " |
| 11:44.11 | ZorbaTHut | "the next major version", I probably mean "2.1" because I don't want to break stuff during the expansion release |
| 11:44.25 | ZorbaTHut | but normally the deprecation cycle will be faster |
| 11:45.10 | Noshei | but breaking things during xpac release is a good reason to get us all into alpha testing :D |
| 11:46.02 | Noshei | or I guess not wanting to break things is an equally good reason, lol |
| 11:47.13 | Noshei | Though I'm kinda surprised they have now officially said Fall 2012 considering how unfinished they have made it sound in the live streams |
| 11:47.44 | ZorbaTHut | Eh, it's us. We're fast at doing things. :) |
| 11:49.15 | Noshei | well if they stay with a month in between each soul being revealed that puts the game into november or december, which is pushing into winter 2012, imo |
| 11:52.40 | Noshei | heres hoping it doesn't take that long though |
| 11:53.18 | Noshei | so besides the guild api and deprecation anything else coming with 1.10? |
| 11:56.13 | Noshei | oh and the text frame fix, looking forward to that one |
| 11:58.04 | ZorbaTHut | keep watching the PTS, as always ;) |
| 12:02.02 | Noshei | bah the PTS is too slow though |
| 13:14.04 | Baanano | hi |
| 13:50.27 | Noshei | hey Baanano |
| 13:50.44 | Baanano | hi noshei |
| 14:19.02 | *** join/#riftuidev Noshei_Mobile (~Noshei@c-67-161-146-244.hsd1.co.comcast.net) |
| 15:06.23 | Thorarin | \o/ |
| 15:06.32 | Thorarin | Took the rest of the week off |
| 15:36.25 | *** join/#riftuidev g0urra (~g0urra@unaffiliated/gourra) |
| 15:41.33 | Thorarin | Erhm, I'm getting confused again |
| 15:41.48 | Thorarin | When you get a performance warning, the code still executes normally right? 0.o |
| 15:42.52 | Thorarin | Because right now I have some code I run with xpcall which intentionally generates a performance warning.. it never seems to return |
| 16:02.59 | *** join/#riftuidev Imhothar (miranda@ppp-188-174-76-221.dynamic.mnet-online.de) |
| 16:34.40 | seebs | I am not quite sure. I *think* the idea is that performance warnings are just diagnostics, it's only the hard limit that starts breaking stuff. |
| 16:35.18 | seebs | As to scheduling: The whiteboard list from way back when seemed to suggest an anticipated 1.11 before XP1, but that may have changed. |
| 17:28.03 | Thorarin | That's what I thought too seebs (since they are warnings), but I can't explain the behavior I'm seeing atm |
| 17:31.50 | Imhothar | You mean, like having performacne kills after API calls? ;) |
| 17:37.26 | Thorarin | Well, not kills for me |
| 17:37.40 | Thorarin | But warnings, on a call that normally takes 0.2ms |
| 17:38.57 | Thorarin | There is some other code, but it's of little significance. Every API call I potentially yield if the doggy time gets below 30ms |
| 17:39.50 | Thorarin | That cutoff is configurable, so I was now working on detecting the performance warning and suggesting to the user to increase the setting |
| 17:40.06 | Thorarin | Not sure what else to do atm :P |
| 17:40.45 | Thorarin | Anyway, while I was trying to implement that, I noticed the code never gets executed when a warning had occurred |
| 17:42.33 | Thorarin | That effect also stops the function from being removed out of the queue the coroutine executes... so it kept running it over and over |
| 17:43.00 | *** join/#riftuidev Imhothar (miranda@ppp-188-174-76-221.dynamic.mnet-online.de) |
| 17:43.32 | Thorarin | But strangely enough without executing the statement just before the call to the function either, so I'm thoroughly confused atm ;) |
| 19:54.51 | *** join/#riftuidev Imhothar (miranda@ppp-188-174-76-221.dynamic.mnet-online.de) |
| 20:59.41 | Thorarin | *sigh* second off-spec relic weapon, still no mainspec weapon :P |
| 22:15.33 | *** join/#riftuidev g0urra_ (~g0urra@unaffiliated/gourra) |
| 23:17.44 | Baanano | see you tomorrow |
| 23:42.03 | ZorbaTHut | thorarin, warnings definitely shouldn't kill execution - if they do, something's broken |
| 23:42.17 | ZorbaTHut | that said, note that the warning won't actually trigger until after the event handler returns |
| 23:42.31 | ZorbaTHut | it's buffered internally until it has a known safe point to trigger the warning |