Aaron Klotz
Aaron Klotz
Signed-off-by: Aaron Klotz
### What are you trying to do? This came out of a support issue. The user has an uncooperative firewall and ended up running `tailscaled --port` manually. They would like...
Once https://github.com/tailscale/corp/issues/6991 is done, we need to handle this on the client side.
… and ensure that the device interface list is explicitly queried immediately after notification registration Tailscale has several open issues concerning WinTun adapter installations that hang indefinitely, stuck waiting on...
Per [this discussion](https://github.com/tailscale/walk/pull/59#discussion_r1561541805), we still have room for improvement concerning app init. Ideally we'd have `walk.App()` callable from within appInits, and still have some sort of mutual exclusion around `InitApp`...
In the review for [this PR](https://github.com/tailscale/walk/pull/59), @nickkhyl points out that it would be nice if `AppendToWalkInit` could accept functions that return `error`s so that failures could be propagated up to...
This is just unsafe. Now that we're able to recycle action IDs, I can't see a reason to keep it. Let's use the GC: add finalizers to `Action` that synchronize...
eg let's say I've got an `HICON` from something (maybe I created it myself via `CreateIcon`) and create a `*walk.Icon` from it. Walk doesn't handle dpi scaling etc like it...
eg Tailscale's device menu on large tailnets. The scroll buttons are tiny. I'm not even sure how owner-drawn menus deal with this... or even if they can.
Right now there's no way that I can see to do this because `HWND_MESSAGE` is a special `HWND` value which cannot be made into a `walk.Window`.