I really like this idea! I definitely want to merge this in. Would you mind if I changed the interface a bit?
I'm thinking that matching the way UI Automation specifies rects would be good. It does the same thing as CGRect, {origin: {x: 1, y: 2}, size: {320, 200}}, something like that.
Also, what would you think of naming it frame instead of boundsArea, too? By setting up a rect, it reminds me of frames for UI Views.
Just trying to figure out ways to keep the API consistent with Cocoa Touch. Let me know what you think.
I really like this idea! I definitely want to merge this in. Would you mind if I changed the interface a bit?
I'm thinking that matching the way UI Automation specifies rects would be good. It does the same thing as
CGRect
,{origin: {x: 1, y: 2}, size: {320, 200}}
, something like that.Also, what would you think of naming it
frame
instead ofboundsArea
, too? By setting up a rect, it reminds me of frames for UI Views.Just trying to figure out ways to keep the API consistent with Cocoa Touch. Let me know what you think.