57 lines
1.5 KiB
Markdown
57 lines
1.5 KiB
Markdown
# Windows UI / device identity update — v0.1.3
|
|
|
|
## 1. Chinese UI font
|
|
|
|
The Windows sender no longer relies on egui's default font for Chinese text.
|
|
It loads a TrueType font (`.ttf`) at runtime and installs it as the first
|
|
Proportional and Monospace font fallback.
|
|
|
|
Lookup order:
|
|
|
|
1. `QFT_FONT_PATH`
|
|
2. `qft-ui.ttf` next to the executable
|
|
3. `assets/qft-ui.ttf` next to the executable
|
|
4. `./assets/qft-ui.ttf` from the current working directory
|
|
5. common Windows Chinese `.ttf` files
|
|
|
|
For development, the most deterministic setup is to put your own Chinese-capable
|
|
TTF at:
|
|
|
|
```text
|
|
windows/assets/qft-ui.ttf
|
|
```
|
|
|
|
No font file is bundled by this project.
|
|
|
|
## 2. Device display
|
|
|
|
The Windows sender now displays:
|
|
|
|
```text
|
|
本机设备:DESKTOP-XXXX
|
|
传输设备:DESKTOP-XXXX → Android 光学接收端 · 正在传输
|
|
```
|
|
|
|
The MANIFEST payload now appends:
|
|
|
|
```text
|
|
sender_device_len: u16
|
|
sender_device_utf8: bytes
|
|
```
|
|
|
|
The Android app displays both endpoints, for example:
|
|
|
|
```text
|
|
传输设备:DESKTOP-XXXX → Xiaomi 15
|
|
```
|
|
|
|
The field is appended to the end of the old MANIFEST payload, so the new Android
|
|
parser remains compatible with v0.1/v0.1.2 manifests.
|
|
|
|
## Important limitation
|
|
|
|
Windows -> Android is intentionally a one-way optical channel. The Android phone
|
|
does not send any ACK or identity back to Windows, so the Windows sender cannot
|
|
automatically know the exact receiving phone model. The Android side can show
|
|
both the sender PC name and its own local device model.
|