-
-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add information from WPF VisualTreeHelper #28
Comments
Hi Roman, I had the same Idea a while ago with a project spike called "XAML Inspector" which allows you to connect to a running, or lauch an new WPF application and then remote-control it through an agent.dll that gets loaded into the app and communicate through HTTP. This could now merge into a new XAML-provider of FlaUI that could be written for UWP, WPF, WP10. Regards |
This is a different approach than the one from WPFInspector right? But I like the idea having a small agent so that not the whole FlaUI needs to be injected. Do you have some code already? |
Yes. WPF Inspector injects the whole application including the UI with all it's problems (style inheritance,...). The idea of XAML inspector was to have a small agent, that is easy to port to any XAML based platform that streams the data through a web-socket connection to the UI (or the FlaUI provider) that allows you to remote-debug or control an application. |
@ChristianMoser Did you start something already for the agent? Is there maybe some experimental code around? |
In WPF, there is the VisualTreeHelper which allows you to browse the whole visual tree and get information out of it.
It is possible to attach to an application and get the visual tree out with information like text styles.
See https://wpfinspector.codeplex.com or https://snoopwpf.codeplex.com for examples.
We should add this as well to provide additional information for WPF applications.
The text was updated successfully, but these errors were encountered: