11:22:36jackdanielwe mat still have a class backing the type
11:23:05jackdaniellike in previous version, if having them '* is problematic for some reason
11:25:21jackdanielI had a brief idea to have region parameter instead of xy, but that feels like overengineering
12:50:45scymtymi don't think '* will cause problems
12:51:47scymtyma region parameter would allow an input context (blank-area :sheet SHEET :region REGION) and subtyping could make sure that only clicks within that region would be acceptable. but yeah, maybe leave that for later
12:53:05jackdanielI think that if we decide on x/y vs region once, we need to commit to it for sake of compatibility (assuming we document it or examplify in demos)
13:56:21scymtymthen we have to implement the region variant in order to evaluate it
13:58:00jackdanielthat's only if we want to implement it -- I've rejected the idea (when I was thinking about it) because I've concluded that if someone wants a region on a sheet, then it should be properly presented with a distinct presentation type
13:58:33jackdanielit is possible to construct artificial use cases - I didn't come up with a practical one though