We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Follow up from #907, related to #640, #41, #990, #846, #881, #911
Issues:
group-leader
prop_get
XSync
X11_prop_get
can-focus
call_setup()
WM_STATE
iconic
notify::
x11_get_server_time
_NET_WM_ACTION_CLOSE
WM_CLIENT_MACHINE
add_event_receiver
remove_event_receiver
The text was updated successfully, but these errors were encountered:
A lot refactoring was done as part of #1995
Sorry, something went wrong.
No branches or pull requests
Follow up from #907, related to #640, #41, #990, #846, #881, #911
Issues:
group-leader
code calls gtkprop_get
is called from anXSync
context we manage, should never call into GTK - it doesn't, but we should make certain it never willprop_get
intoX11_prop_get
and inject X11 dependency?can-focus
is not usedcall_setup()
is inconsistentWM_STATE
still a bit of a mess..iconic
: boolean is not good enough? (need to map Withdrawn.. old clients can't do it)notify::
in callers?x11_get_server_time
-> replace with native X11 call?_NET_WM_ACTION_CLOSE
WM_CLIENT_MACHINE
: use XGetWMClientMachineadd_event_receiver
/remove_event_receiver
: use WeakHashMap to workaround gtk3 lack of set_data, would need route_event anyway - mehThe text was updated successfully, but these errors were encountered: