Hi Piero,
Yes, I think that would be useful. I’ve logged a read-only Window.FocusedControl property for desktop apps. It will return the Objo control currently holding keyboard focus in that window, or Nothing when there isn’t one. That should help when one shared routine needs to work with whichever control is active.
For your preference-saving example, I’d use the existing FocusLost event on each relevant field. In the handler, Me is the field that just lost focus, so you can pass it to a shared save routine. By that point, Window.FocusedControl might already be the next control.
https://feedback.objo.dev/feature/1628