Yukari Hafner

I'm afraid I still don't understand the purpose of your proposed changes. So instead, let me try and explain what the idea is behind the component and data protocols again,...

I mean if you have something like ``` (let ((a 0)) (alloy:represent a 'alloy:slider) (setf a 1)) ``` There's no way for the slider to know that `a` has changed...

Well yes, it's unavoidable, but the question remains whether it's worth it to try and bridge the gap at all, or whether that will just confuse users needlessly and create...

The point is that in alloy the focus tree and the layout tree are explicitly separate. This does create more work as you need to manage both, but is necessary...

I agree that there should be ways to create the UI more easily, but there simply isn't any redundancy here.

Yeah, the fond backend does not calculate cursor positions correctly. It is correct in the msdf backend, but for that the atlas generation is still broken in the 3b/sdf library....

That is the repo, though not the right branch (msdf). We use it here: https://github.com/Shirakumo/alloy/blob/master/renderers/opengl/msdf.lisp#L112 The issue is complex and I'm waiting for @3b to get back into working on...

@3b The problem mentioned in this ticket is in the fond backend, which has nothing to do with the msdf atlas. It's just doing a bad computation on the glyph...

Yeah, I agree, though it might be nice to be able to influence how the autorepeat works (constant, linear, exponential, multiplier, etc.) Autorepeat is also sorely missing from the text...

There are definitely cases where it is vital to distinguish between the first event and repeats. As for how to handle the repeat behaviour, I was thinking more along the...