Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 02 2016 16:31
    @chamons banned @IfErrThrowBrick_twitter
Rolf Bjarne Kvinge
@rolfbjarne
yes, [NullAllowed] will make the generated code accept nulls. We're working on generating the nullable annotations too, but that's still work in progress.
Tomáš Linhart
@TomasLinhart
this is only getter so there is not accepting, it is only returns
Rolf Bjarne Kvinge
@rolfbjarne
then the generated code wouldn't change, it may still return null
Sebastien Pouliot
@spouliot
nullability progress is tracked in xamarin/xamarin-macios#6154
Sebastien Pouliot
@spouliot
I just updated the issue, to answer the last question.
Sören Nils Kuklau
@chucker

is there something about CSS styling in the pipeline that works differently than XAML styling? i'm seeing a bug where a stylesheet isn't applied in some cases, but XAML is, and i'm not really sure how to break it down into a test case

if anyone's wondering, i eventually found the bug (or one of them?), and filed it at xamarin/Xamarin.Forms#10484

which brings me to my next question: is there a way to specify platform-specific CSS? basically, this:

    <ContentPage.BackgroundColor>
        <OnPlatform x:TypeArguments="Color">
            <On Platform="macOS">Transparent</On>
            <On Platform="iOS">White</On>
        </OnPlatform>
    </ContentPage.BackgroundColor>

e.g., something like

^contentpage[on-platform=macOS] {
    background-color: transparent;
}
if not, should i file that as a feature request?
chucker @chucker shrugs and files
Sebastien Pouliot
@spouliot
here might not be the best place to ask about XAML :smile: or even XF - we know what it is but it’s not our area of expertise
Sören Nils Kuklau
@chucker
oh right, this isn't XF. sorry!
Sebastien Pouliot
@spouliot
np :smile:
Rolf Bjarne Kvinge
@rolfbjarne
the main problem is to verify the fix
Alex Soto
@dalexsoto
Yep we discussed that yesterday, Apple is very likely returning a custom subclass
and since we cannot match we are trying to instantiate BGTask but since it is abstract we can't
Rolf Bjarne Kvinge
@rolfbjarne
yep, exactly
Manuel de la Pena
@mandel-macaque
@rolfbjarne that is the conclusion we arrived
@rolfbjarne do I like it.. not really, but is the only way
:confused:
Julio César Rocha
@JunielKatarn

Hi.
Does anybody know how to set up a Xamarin Forms app to run on macOS 10.9?

xamarin/xamarin-macios#8556

Sören Nils Kuklau
@chucker
XF is barely running on modern macOS, let alone a release that's seven years old
the system requirements you cite are for Xamarin.Mac, not Xamarin Forms
as your link to contentViewController shows, that's a new API starting in 10.10. my guess is XF doesn't depend on it too much, so you can probably make a fork and possibly a PR to make it compatible to work without contentViewController, but my money is on it isn't worth it — Xamarin Forms on macOS is in preview, supporting it isn't a high priority, and supporting rather old macOS at this point definitely isn't a priority
Julio César Rocha
@JunielKatarn

That's too bad. I hope the XF team will at least acknowledge this and state the minimum supported version clearly.
That said, I tried my app in macOS 10.10, and it still crashes, but the offending selector IS supported in that version.

I'll follow up in a new GitHub issue.

Sören Nils Kuklau
@chucker

state the minimum supported version clearly

XF on macOS isn’t supported at all; it’s in preview.

Julio César Rocha
@JunielKatarn
Yeah, I should have said "current targeted".
Sören Nils Kuklau
@chucker
Hm, yeah, https://github.com/xamarin/Xamarin.Forms/wiki/Platform-Support should list per-platform requirements and doesn’t
Julio César Rocha
@JunielKatarn

Neither does the per-platform "Report".
I did find something useful in the .NET AppKit docs:
https://docs.microsoft.com/en-us/dotnet/api/appkit.nssplitviewitem.minimumthickness?view=xamarin-mac-sdk-14

There seems to be an annotation declaring the supported OS version explicitly.

Do you know who owns the AppKit .NET projection, and specifically, the ObjCRuntime types?

Rolf Bjarne Kvinge
@rolfbjarne
For issues with the AppKit bindings, or in the ObjCRuntime namespace, you can file bugs in https://github.com/xamarin/xamarin-macios/issues
gonzobrains
@gonzobrains

Hi. First time visitor here. I'm dead in the water with trying to open storyboards right now. Originally my error was due to the render timing out. I upgraded to VS 2019 and now I get

"An error occurred while initializing the frame's content
System.ArgumentException: 'ZoomMenu_100 ' is not a valid value for property 'Name'."

I upgraded to VS 2019 Preview (which is supposed to fix this) but still get the error. What can I do now?

Brandon Blue
@DarkBlue_X2_twitter
Hello, does Mono currently work with MacOS Catalina 10.15.4?
Sören Nils Kuklau
@chucker
sure
Brandon Blue
@DarkBlue_X2_twitter
Can't figure out how to get it to work for the life of me
Sören Nils Kuklau
@chucker
i have Mono 6.12 on here
installed via Visual Studio for Mac
Brandon Blue
@DarkBlue_X2_twitter
So I downloaded the Visual Studio .pkg in my Downloads folder
when I right click to open I get this message
The operation couldn’t be completed. (com.apple.installer.pagecontroller error -1.)
Is this the correct installer file?
MonoFramework-MDK-6.8.0.123.macos10.xamarin.universal
Sören Nils Kuklau
@chucker
6.8 sounds old, i think?
Brandon Blue
@DarkBlue_X2_twitter
It seems to be the most updated one?
Sören Nils Kuklau
@chucker
hrm
Brandon Blue
@DarkBlue_X2_twitter
Sören Nils Kuklau
@chucker
in any case, even 6.8 should work in Catalina
but updating Visual Studio should give you a newer one
can you right-click, Open With, and pick Installer there?
Brandon Blue
@DarkBlue_X2_twitter
yep