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
[WPF]Set the name of a control #562
Conversation
* Implemented extended interface in WPF/WidgetBackend. This change is important for UI automation/UI testing tools like Microsoft Test Manager. These tools use the name of a control to identify it, without setting a name, at least Microsoft Test Manager will use the first control of that type that it encounters (for example: the minimize button)
Anyone? |
…den by a control which in turn makes it possible to set the tag property on the native control itself.
Great idea, but:
|
For 1.: Because I didn't want to break existing functionality while I also didn't want to implement it for every control. For 2.: true. Forgot that I adjusted an interface. That'll take some time... |
For 1.: why would you break existing functionality by adding a |
For 2: Gtk is pretty simple cause all Gtk widgets have a |
For 1: that was about the .Tag property. Not .Name or have I missed something? |
For 1: you have introduced a new |
Partially merged: Name property from 2f45218 (via 4adb26f) I don't know whether the WindowFrame.Tag (btw all FrameworkElements have a Tag property so maybe not only Windows should implement that) property might be useful. But there is nothing comparable in Gk/Mac, so it would only work with Wpf wich wouldn't make much sense to implement at all. |
This change is important for UI automation/UI testing tools like Microsoft Test Manager. These tools use the name of a control to identify it, without setting a name, at least Microsoft Test Manager will use the first control of that type that it encounters (for example: the minimize button)