James Blacklock

Yeah, I hadn't thought through all of the details like jump offsets, but that sounds basically like what I was looking for. I may try to (partially) implement this as...

I came up with a somewhat hacky solution for the lack of a `blur` equivalent: export TableCell := Rectangle { property input; property active; property text; property placeholder-text; property horizontal-alignment:...

Ok great, I was intending to sync up with the master branch anyway so I will try that. Good point about using a different FocusScope as well. I 100% agree...

I really need some `focused` and `unfocused` callbacks for my project. If I work on implementing this functionality in the library, would it be likely to be accepted?

Also, is there any discussion of this feature that I should be aware of? It looks like `.focus()` gets injected into every element, but I don't see a way to...

Of course, we could simply trigger the callback inside of `ItemVTable::focus_event`, but then you would have to implement it separately for any element that can receive focus.

I'm looking at your `#[vtable]` macro (very cool crate!) and it doesn't appear that there's currently a way to add a default trait impl. Is this true?

It seems that focusability is determined on an ad-hoc basis by returning `FocusEventResult::FocusAccepted`. Thus it would seem that the most practical thing to do is simply add a `callback focused`...

What seems to me would be preferable, though, would be for every item to always get these callbacks. Not sure exactly how to implement that, though.

Could also be added to the `property_declarations` of every `Element`