GUI bug? #333
|
Hi again! |
Replies: 1 comment 1 reply
|
@Jobima1st, real bug, and your video made it a one-look diagnosis. Fixed in the current development build (latest-v4-dev, r3304 or newer). What was wrong: the window watches every click so it can drop keyboard focus when you click a neutral surface. That watcher walks upward from whatever element the click landed on, and it used a WPF call that only accepts ordinary visual elements. The slot type badge's label is formatted text, and clicking formatted text hands the watcher the text fragment itself, which that call rejects by throwing. Hence the error dialog on a plain left click. The walk now routes text fragments through the tree that knows their parent, and the same fix went to four other click handlers in the app that walked the same way and would have crashed on any formatted label. The crash shape is pinned in the test suite so it stays fixed. Nothing about your setup caused this, and no settings were harmed by the dialog. It was purely the click watcher tripping over the badge's text. |
|
seems fixed now, thanks! |
@Jobima1st, real bug, and your video made it a one-look diagnosis. Fixed in the current development build (latest-v4-dev, r3304 or newer).
What was wrong: the window watches every click so it can drop keyboard focus when you click a neutral surface. That watcher walks upward from whatever element the click landed on, and it used a WPF call that only accepts ordinary visual elements. The slot type badge's label is formatted text, and clicking formatted text hands the watcher the text fragment itself, which that call rejects by throwing. Hence the error dialog on a plain left click.
The walk now routes text fragments through the tree that knows their parent, and the same fix went to four ot…