JonKazama-Hellion
eca566321a
Reported by Carla: a tell arriving while you are typing pulls the focus away. The interruption is the visible half. The sharp half is that the input buffer belongs to the WINDOW while the send target is read off whatever tab is active at Enter -- so a line typed at one person could leave addressed to whoever just wrote, and in this game losing the keyboard means the next sentence walks the character around. Nothing is revealed now while any chat surface is mid-sentence, in any mode. The tab still appears and still carries its unread mark. The check lives in its own file because the answer has to be identical everywhere: it started inside the reveal plan, and a second pop-out path walked straight past it -- AutoTellTabsService opened windows off its own flag, at tab creation, a tick before the router was ever asked. Those two paths are one now. AutoTellTabsOpenAsPopout and TellAutoOpenMode were two settings for one decision, and the older one won every race, which is why the other looked inert. Config schema 28 carries the old flag forward so nobody's behaviour changes. "Off" went with it: it never stopped the tab from being created -- that is the auto-tell switch -- it only stopped the jump to it, which is what the switch below it does. Also in here, all from the same corner of the code: - Closing a tab was lost in the v2.0.0 rebuild. The trash entry lived in the retired ChatLogWindow menu, and the rebuilt one restored rename, sound, pop-out and pinning but not this. For tell tabs that left no way out at all: IsEditable keeps them out of the settings editor on purpose and points at the context menu, which could not close them either. Pinned tell tabs stay disabled with a tooltip rather than absent. - Re-anchoring the active tab used an unconditional Tabs[0] in three places, and Tabs[0] can be popped out -- so it ran OnTabActivated over a tab live in its own window and stripped its tell binding. With every tab popped, the seed and the re-anchor also fought each other every frame. - PinTab_LimitReached still pointed at "Promote to permanent", removed in May. Spanish said "Desija", which is not a word; Greek left "tell tabs" untranslated; pt-PT broke its own unpin verb. - Pop Out was a hardcoded English literal despite the key existing in all 25 languages since v1.5.6, and the tell-open modes were the last English display names in the plugin. - Segmented setting rows measured 200px flat, which cut German labels in half. They size to their longest label now. - Metrics.Scale still called GlobalScaleSafe. It is an alias for GlobalScale in current Dalamud, and dropping it clears the last compiler warning in the project.
22 lines
995 B
C#
22 lines
995 B
C#
namespace HellionChat.Ui.Windows;
|
|
|
|
// Focus contract shared by the main window and each pop-out so the keybind tail
|
|
// can route channel-set / REPLY / prefill to whichever surface currently owns the
|
|
// input focus, without the KeybindManager reaching into either window's privates.
|
|
// HasFocusedInput reads the bound InputBar's per-frame focus state; RequestInputFocus
|
|
// only arms the one-frame Activate flag (ImGui focus is frame-bound — never call
|
|
// SetKeyboardFocusHere from the framework thread).
|
|
internal interface IFocusableChatWindow
|
|
{
|
|
bool HasFocusedInput { get; }
|
|
|
|
// "The user is mid-sentence here." Focus alone is not enough: a typed line
|
|
// survives a click elsewhere, and stealing the tab out from under it is how
|
|
// half a message ends up addressed to whoever just said hello -- the input
|
|
// buffer belongs to the WINDOW, but the send target comes from whichever tab
|
|
// is active at Enter.
|
|
bool IsInputBusy { get; }
|
|
|
|
void RequestInputFocus();
|
|
}
|