Mouse Cursor

[bdlukaa]

Add mouseCursor to MacosThemeData. By default, on Apple platforms, MouseCursor.defer (no cursor) is used. On the other platforms, SystemMouseCursors.click is used.

Closes #139

Pre-launch Checklist

• I have run dartfmt on all changed files
• I have incremented the package version as appropriate and updated CHANGELOG.md with my changes
• I have added/updated relevant documentation
• I have run "optimize/organize imports" on all changed files
• I have addressed all analyzer warnings as best I could

[GroovinChip]

@wilsonowilson does this look good to you?

[wilsonowilson]

Not sure how I feel about having cursor in the theme. Cursors don't have anything to do with theming, and as such, both ThemeData and CupertinoThemeData have no cursor property. Instead, cursors are provided to the widgets that need them alone.

But I understand the problem the PR is trying to solve... automatically providing a cursor to widgets that need it based on platform. I suggest creating a separate widget that handles this, perhaps an InheritedWidget called CursorConfiguration. That way we'd be able to call CursorConfiguration.of(context) to access things like clickableCursor? and disabledCursor. LMK what you think.

[GroovinChip]

Not sure how I feel about having cursor in the theme. Cursors don't have anything to do with theming, and as such, both ThemeData and CupertinoThemeData have no cursor property. Instead, cursors are provided to the widgets that need them alone.

But I understand the problem the PR is trying to solve... automatically providing a cursor to widgets that need it based on platform. I suggest creating a separate widget that handles this, perhaps an InheritedWidget called CursorConfiguration. That way we'd be able to call CursorConfiguration.of(context) to access things like clickableCursor? and disabledCursor. LMK what you think.

I agree with you, that seems like a better approach.