Profile_bird

Hey there! matelich is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving matelich's tweets.

Already using Twitter
from your phone? Click here.

matelich

  1. Not sure what will happen to my brain after 12 days off work
  2. @thinkgeek Oh mama. My tauntaun test tube baby really needs to simulate a birthing experience, and that sleeping bag will do the trick!
  3. So many RelayCommand classes, so many little differences, all with the same classname.
  4. @LBugnion yeah, for most properties I am just binding to the model. It's just the ones where the vm modifies the presentation. Thanks
  5. @LBugnion My model is a db entity that I'm updating from other viewmodels, I'd like to avoid duplicating logic as much as possible
  6. @LBugnion Yeah, was just hoping there was some coolness. I remember Josh Smith has some handy thing for watching INPC. I'll look that up.
  7. @lbugnion Is there some handy tool in MVVM Light for situations where your model is INotifyPropertyChanged so the VM can react?
  8. A lazy Saturday with the family. Probably try to get some work in at naptime, though. WPF and cookies ;)
  9. This is the best batch of Junior Mints evar
  10. Good night, eliza and Abraham. I <3 U
  11. @LBugnion just send an ipc message. A dialog would be cool. Thx
  12. @lbugnion http://stackoverflow.com/questions/1878362/mvvmlight-eventtocommand-and-wpftoolkit-datagrid-double-click thanks!
  13. The power of Twitter! Laptop now working.
  14. Bah, iPhone on seatac free wifi but #win7 x64 fails
  15. @TacOps1 risky venturing out in public like that
  16. @TalkToQwest, No mis-dials yet today. Keep forgetting to make test calls, sorry. However a friend went to gonzaga trying to call us today
  17. RT @lesnikowski: "70% of respondents [at MS] said they were dissatisfied with VS performance" (http://is.gd/5eFrd) #vs2010
  18. Note to self: Tweet all Qwest issues. Phone support is for chumps.
  19. Thanks, @TalkToQwest
  20. I liked blaming the destination phone number, even though its spread across at least 4 numbers. Either qwest bug or bad phone. hmmm