Seems like there is a tradition of posting keyboard builds of the year amongst the #SelfMadeKeyboardsInJapan community.
Here are mine for 2019 ๐. Two Cornes left to build for one each month. ๐ Think that should be a good number to stop? ๐ต
Thanks @foostan.
transfer to an โunverified external Codex thread,โ even when Task A explicitly requested the response. Incoming communication works; replies fail. This breaks coordinator workflows and increases duplicate-mutation risk. Expected: same-account/same-host task replies inherit
Codex desktop 26.908.40834 build 8881 has a reproducible cross-task messaging failure. Task A can send a delegation to Task B, but Task B cannot reply to the exact authenticated source task when the response contains repository status. send_message_to_thread rejects it as
@mattgemmell Thanks. I designed the case and it ran as 2 group buys so far. Search IMK Corne and you may find some on second hand markets. Been too busy to start 3rd group buy.
Paw ยท The most advanced REST & GraphQL API client for Mac https://t.co/9urIFDWKje ยท Our crazy๐คฏ 2021 Black Friday offer: Retweet this and get a free Paw license (worth $49.99) ๐
@mecid To clarify the first version works and the second version does not. It seems if we conditionally return anything that is not the NavigationLink, then Push animation will get disabled.
@mecid I read your article on Lazy Navigation and was interested to try it out. However, it seems to interfere with the Push animation of NavigationStack. The destination appears instantly instead of being pushed on. Did something change to break this?
@mecid Seems like SwiftUI (at least on Xcode 13 GM that Iโm still running) doesnโt like it when the NavigationLink is swapped in/out.
I get the same issue when I change my LazyNavigationLink body to this:
@mecid Yup. I have that already. Could it be the failable init?
I took your idea and tweaked it like this and now itโs working great.
Nice idea, BTW. Going through your other posts now.