mje Posted January 11, 2012 Report Share Posted January 11, 2012 Is there any reason we can't step into a property node when debugging? Or for that matter step over individual properties of a node then step into the one of interest? As it stands now, I have to find the accessor method by hand, open it up and drop a breakpoint if I want to continue single stepping. Not a terrible inconvenience, but it can slow things down. Especially if reentrancy is involved. Just thinking out loud here. Is there something that would make this impossible? Quote Link to comment
mje Posted January 11, 2012 Author Report Share Posted January 11, 2012 Oh man, I feel like a fool. Posted this before checking my rss feed and seeing Norm's earlier post. Oh well... Quote Link to comment
crelf Posted January 11, 2012 Report Share Posted January 11, 2012 Norm's tool looks pretty good, but I think it only works at edit time. Quote Link to comment
Yair Posted January 11, 2012 Report Share Posted January 11, 2012 For those who haven't seen it, Norm's tool is here and there's also a link for an idea to make this easier, so you should go vote for that. Quote Link to comment
Mr Mike Posted January 11, 2012 Report Share Posted January 11, 2012 The main reason that you can't debug into class property nodes is that we didn't have time to implement it. Quote Link to comment
Norm Kirchner Posted January 11, 2012 Report Share Posted January 11, 2012 Oh man, I feel like a fool. Posted this before checking my rss feed and seeing Norm's earlier post. It's ok, blame me for not getting it out earlier. Or for your penance, you can go ahead and implement reasonable error tracking Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.