you can use Silk.NET on .NET 6+ Android and iOS, but not MAUI today
you can use Silk.NET on .NET 6+ Android and iOS, but not MAUI today
QI take it that also includes regular WPF?
Qah perfect thats good to hear
Qreally loving it so far and would like to also make a port for mobile soon
Pyeah no support for that yet, it’s all technically possible (even MAUI) but really we want to publish a package that makes it easy, we don’t want our users writing thousands of lines just to bridge their UI framework and Silk.NET
Qi was figuring perhaps the GL context could be created from an existing control in there
Qyeah thats very understandable
Qim already grateful theres an option for android
Pon WinForms yes because they make it dead easy, WPF is so much more complicated because you’re trying to make a GL context within a D3D9 window
Qahh.....
Pwhich is possible! It is just extremely difficult
Qyeah they kept telling me to use OpenTK https://github.com/opentk/GLWpfControl
GitHub
A fast native control for OpenTK 4.x + 3.x on WPF. - GitHub - opentk/GLWpfControl: A fast native control for OpenTK 4.x + 3.x on WPF.
Qbut i like silk.net
Qthe alternative is i find a way to host the current silk.net window within wpf somehow?
Qbut it's like you said, all very hacky
Qand i'd prefer MAUI then anyways
Pyeah so that one (as of recently) does basically what we’d be doing, in that it uses GL_NV_dx_interop.
Pbut we want to take time to make it all generic so we can mop up WinForms, WPF, MAUI, and Avalonia all at once
Qam i wrong to assume MAUI would be a great base for general cross-platform stuff?
Qbecause MAUI seems to be applicable also for phone
Qim glad they finally bridged that in .NET with MAUI
PI mean yeah, but also MAUI is a UI framework and most of our users are developing fullscreen games for those platforms, rather than hybrid apps with a bit of 3D and a bit of system UI
Phence why we do support mobile but only using our cross-platform IView abstraction
Qgotcha, thanks for the info!
Pno worries! this is all planned, and I wish we could get to it sooner, but there’s lots of behind the scenes work happening rn (mostly on 3.0) that will hopefully pave way for this in the future
PQwell im keeping my eyes open! seems like the rework is super exciting (:
Kthats the hope!
Alol this was just starting to annoy me right
Acause piegfx is taken by some 12 year old youtube channel so i figured this was next best
Ai was annoyed until i realized that it was taken by me
Ai guess i forgot i existed
PLOL
Anow what tf is the email for this account
AHUH WHEN DID I MAKE THIS
Mghdfrtghydftg
Pnearly there
Knice!
Ki just got reminded of https://github.com/dotnet/runtime/issues/2162 and now im sad again that that isnt in
GitHub
Edit by carlossanlop: I marked this issue as up-for-grabs. If you're interested in taking it, please read this comment. This feature is fully implemented already, but the only thing pending to ...
Pit's API approved, go implement it and it'll be in .NET 9
Kfair lol
Kalso the fact that you cant call interface statics on the implementing type unless its an abstract in general or a virtual on a type parameter is so annoying still
Klove having a static method that will proabably get duplicated in a ton of structs because an interface static wouldnt be usable
Mstill so pissed that DictionarySlim and MultiValueDictionary from corefxlab were abandoned
Pcorefxlab wow that's a blast from the past
Mi still depend on it for niche use cases
Mi should fork and vaguely support it
Mcurrently need to use dictionary in render thread more than once per frame and it's like... 
Mstring dictionary too! all of the worst case scenarios!
Pman I love Microsoft.Extensions.Configuration but I also hate it
P
