You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2024. It is now read-only.
Writing down this idea just so I don't forget: one thing I've noticed is most implementations of WinHandler end up containing a ton of Options, which only get filled in after connect() is called. If we changed set_handler to take a FnOnce(&WindowHandle) -> WinHandler as an argument instead of an explicit WinHandler, perhaps we could handle some complexity for the user? (Although the user must be careful to not call any methods of the WindowHandle during initialization that would require the WinHandler to exist.)
The text was updated successfully, but these errors were encountered:
Writing down this idea just so I don't forget: one thing I've noticed is most implementations of
WinHandler
end up containing a ton ofOption
s, which only get filled in afterconnect()
is called. If we changedset_handler
to take aFnOnce(&WindowHandle) -> WinHandler
as an argument instead of an explicitWinHandler
, perhaps we could handle some complexity for the user? (Although the user must be careful to not call any methods of the WindowHandle during initialization that would require the WinHandler to exist.)The text was updated successfully, but these errors were encountered: