-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve NSAttributedString ctors in foundation.cs #14489
Labels
enhancement
The issue or pull request is an enhancement
Milestone
Comments
chamons
added a commit
to chamons/xamarin-macios
that referenced
this issue
Mar 24, 2022
- Unlike the rest of my recent work, this is all done by hand, so please review closely. - Part of dotnet#14444 - Do note that there still are defines left, as there are many "almost same but not exactly" between platforms. - Some of these only differ on ref/out - Filed the rest as dotnet#14489
chamons
added a commit
that referenced
this issue
Mar 31, 2022
- Unlike the rest of my recent work, this is all done by hand, so please review closely. - Part of #14444 - Do note that there still are defines left, as there are many "almost same but not exactly" between platforms. - Some of these only differ on ref/out - Filed the rest as #14489 Co-authored-by: Manuel de la Pena <[email protected]>
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Apr 7, 2022
…otnet#14489. There were numerous differences in the managed API for NSAttributedString between macOS and other platforms: most notably macOS would use 'out' parameters, while the other platforms would use 'ref' parameters (possibly due to this being very old API, and we didn't have proper support for 'out' attributes when it was implemented). This PR unifies the API between all platforms when it can (either now or in XAMCORE_5_0). It's hard to determine whether the changes don't break the API: api-diff is happy locally, but the results on the bots will be the final determination. Fixes dotnet#14489.
I had a look at the NSAttributedString API, and there is significant room for improvement. That said, it seems to be possible to do it without breaking anything, so I'm postponing to .NET 7. |
rolfbjarne
added a commit
that referenced
this issue
Nov 15, 2022
Part of #14489. Co-authored-by: GitHub Actions Autoformatter <[email protected]>
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Nov 23, 2022
…API definition. This simplifies the code a little bit. Ref: dotnet#14489
This was referenced Nov 23, 2022
rolfbjarne
added a commit
to rolfbjarne/xamarin-macios
that referenced
this issue
Dec 6, 2022
… to match Apple's headers. This allows us to unify the code between all platforms. Also add all the NSAttributedStringDocumentAttributeKey values we haven't bound yet. There are no changes in the public API, because I'm only changing internal types. Ref: dotnet#14489.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During the great breaking change API scrub, one API was missed in foundation.cs.
We have a sub-optimal API in
initWithURL:options:documentAttributes:error
due to issues in iOS 9, which we aren't supporting anymore.I started a patch to fix this:
https://gist.github.com/e5bf4dae26f2accdaf4b6a9de76ed206
but ran into time box issues and it started getting complicated in a mechanical PR. I decided to punt it for now, thus this issue.
The text was updated successfully, but these errors were encountered: