|
That's... theoretically easy enough (that's essentially the MXCFB refresh rectangle, so, the data is there), in practice, a tiny bit more annoying, because the functions already return a specific data type that's already being used for something besides error reporting (the next viable top position, either in the form of a row number or a top margin value).
Meaning this would have to be implemented manually in each fn, and it'd need to be stored somewhere to make it available to API users for feature parity.
Also, that'd be *fb* coordinates, not *input* coordinates.
|