We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is some blind trust regarding what assemblies and assets are loaded at runtime (and their Uri), especially for beginners.
A new tab in DevTools, called "Binaries" (ideally a better name...) which has the following features:
Making this separately available as a third-party component similar to DevTools.
There is already a prototype at https://github.com/stevemonaco/AvaloniaDemos/tree/master/Debugging which has some showcase videos. Some code/UI cleanup and extra testing (multiple assembly projects) will be needed.
Font Name IDs are not accessible through Avalonia or HarfBuzzSharp, but I can P/Invoke libHarfBuzzSharp to get that information.
libHarfBuzzSharp
I would integrate and PR the acceptable features into DevTools.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
There is some blind trust regarding what assemblies and assets are loaded at runtime (and their Uri), especially for beginners.
Describe the solution you'd like
A new tab in DevTools, called "Binaries" (ideally a better name...) which has the following features:
Describe alternatives you've considered
Making this separately available as a third-party component similar to DevTools.
Additional context
There is already a prototype at https://github.com/stevemonaco/AvaloniaDemos/tree/master/Debugging which has some showcase videos. Some code/UI cleanup and extra testing (multiple assembly projects) will be needed.
Font Name IDs are not accessible through Avalonia or HarfBuzzSharp, but I can P/Invoke
libHarfBuzzSharp
to get that information.I would integrate and PR the acceptable features into DevTools.
The text was updated successfully, but these errors were encountered: