Why user testing works-
So Matt Griffith did a real slick screencast of developing WPF apps in IronPython and using Snoop to break down what's going on behind the scenes. Cool.
Watching the demo though, there's a serious problem- he's relaunching Snoop after every change to update it. This resulted in Rob Relyea noting that Snoop really needed a refresh command.
Actually, Snoop binds F5 to rebuild the visual tree and I also tried to be really smart about auto-updating the tree when it was detected to be out of date (like ctrl-shift-mousing over new elements). But no refresh button.
I'd also like to point out that the auto-update feature allows debugging of popups and such- if you want to inspect the UI of a popup, combobox or such, just ctrl-shift-mouse over the contents. The visual tree in Snoop will switch to be the contents of the new popup and the visuals are retained so even after the popup auto-closes, it can still be inspected.
Snoop has just been updated, refresh button included. Thanks Matt!
So Matt Griffith did a real slick screencast of developing WPF apps in IronPython and using Snoop to break down what's going on behind the scenes. Cool.
Watching the demo though, there's a serious problem- he's relaunching Snoop after every change to update it. This resulted in Rob Relyea noting that Snoop really needed a refresh command.
Actually, Snoop binds F5 to rebuild the visual tree and I also tried to be really smart about auto-updating the tree when it was detected to be out of date (like ctrl-shift-mousing over new elements). But no refresh button.
I'd also like to point out that the auto-update feature allows debugging of popups and such- if you want to inspect the UI of a popup, combobox or such, just ctrl-shift-mouse over the contents. The visual tree in Snoop will switch to be the contents of the new popup and the visuals are retained so even after the popup auto-closes, it can still be inspected.
Snoop has just been updated, refresh button included. Thanks Matt!