-
Notifications
You must be signed in to change notification settings - Fork 62
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
how to get active window title etc. #129
Comments
Interesting use case. Currently aenea doesn't provide a proxy for the That being said, the client does have access to this information. When dragon processes an utterance on the client it needs context from the server to decide what action to take. This context is gathered via a call to the The default x11 server implementation grabs context information here: A quick hack for you might be to call Good luck! |
Hey, thanks for the reply. I solved this by adding a print statement to the server. I'm away from the computer, can somebody close this? Sent from mobile
|
It might make sense to add a non _ method to proxy_contexts for getting the context, since we're already getting it and it should be available. Whenever I've needed this in the past, it's been of the form "Is window foo in the foreground" where foo might be a regex or something, so I just used the ProxyAppContext() and then called match() in cilent code. Breaking window was a deliberate design decision -- Unfortunately the Dragonfly API for it is very MS Windows specific (iirc it also has operations like moving windows that are going to be window manager dependent on linux) and I could not figure out a good way to provide a cross platform implementation as I did for the other Proxy* classes. |
I tried a function action like
but now when I say
diagnostics
, it prints the window title of the client (my Windows VM) instead of that of my X11 app. Can I somehow access the window title of the X11 app?The text was updated successfully, but these errors were encountered: