When I click on it, all is I see is this 3 dots going 1, 2, 3, 1, 2, 3, 1, 2, 3,... I can get into other Communities fine.
Most editors
Same thing still applies - you need to get it past the school admin gatekeeper.
As it is, when we had to teach them HTML, the resources we were given were using PHP at the same time, so I scrapped that and just taught them HTML myself. We never teach more than one concept at a time, so I don't know how these other things found their way into the curriculum/resources.
Yeah, the last time I posted about AI stuff I got my first-ever negative net votes here, but it was news and I posted it. Same here. Alvin Ashcraft also posted a link to it, and I said to him that from what I've seen so far, this isn't going to work out any better for them than it did last time. Maybe next time they might learn to ask developers first, BEFORE saying "Hey developers - we need you!".
Well, it depends how you want to look at it. The TL;DR is the number of outstanding bugs has grown.
I remember in the early MAUI days when people were commenting about there being 2000 open issues - there's now nearly 3,500 open issues. A lot of issues have been closed - there was a period where several I was waiting for got fixed - but even more new ones are getting reported as people transition from Xamarin. A lot of them aren't "reliability bugs" in the sense that it makes the app crash, but there's a whole bunch more missing functionality.
Quite frankly I'm surprised they sunsetted Xamarin as planned. All along I was thinking "there's no way that's gonna happen on that date with this amount of bugs still open", but yep, they went ahead and did it anyway. If it were up to me I'd still be using Xamarin, but I don't have that choice (hence starting up this community to try and reassemble everyone from the Xamarin forum days, and let's get to helping each other out with our bugs and workarounds - I already got 1 solution to a problem from someone here).
To give an idea of the missing functionality (which was working in Xamarin) you still can't bind to properties in your ToolbarItems, cause there's no properties there to bind to! The issue for that is now 2 years old. We were told that we can use handlers for that, but there's no documentation on how to do that (I raised an issue for that too a few weeks ago). As I said, that's not one that causes your app to crash, but you still can't do what you could do in Xamarin yet, so the ToolbarItems look out of place with the rest of your app. FlyoutMenu still has issues too.
People complain that there’s “too many parentheses”. People like to complain about dumb stuff.
😂I'm off on a tangent here, but this made me laugh so much! As a Maths teacher I see all the time people complaining about "this is ambiguous - add more parentheses for clarity!" when the reality is Maths is never ambiguous and they've just forgotten 2 of the most important rules of Maths (meaning we already have the correct amount). 😂 These very same people often put the brackets in the wrong place anyway when they do add them adding/removing brackets
Yeah I'll pop the link to the recording in after, but the advance warning is for anyone who wants to watch live to be able to ask any questions at the time (and also to share the link with anyone who might benefit from watching it. e.g. those still stuck over in the other places).
No, what's silly is to not follow the correct grammar of spelling out an acronym in full the first time. Microsoft does this all the time and you're left not being able to use the document because you have no idea what they're talking about, and they haven't linked to anything about it either. e.g. try Googling COM and let me know how you go with finding out what it means. You should never assume the reader knows what it is. It's gate-keeping.
That doesn't make them trend-setters though - that just makes them big spenders on marketing. i.e. Android wasn't following what Apple did - they'd already been doing it first!
Of course, I rarely hire unteachable folks,
There's not really any such thing as unteachable, just people who are too stubborn to admit they could learn a thing or two (or even worse, those who rebel against being told what to do).
Again you're talking about switches. The thread is about normal buttons which have 2 states (the example being given is a button which can be a play button or a pause button depending on the current state). Buttons aren't like check-boxes, switches are. A button triggers an event, check-boxes don't. e.g. on a settings page, you tick all the check-boxes you want first, then click on the Save (or Cancel) changes button - one event for multiple changes. You don't tick a check-box to start playing something, you press a play button (which in this case would then change into a pause button).
Not if the globe has blown out, in which case you need the switch to indicate which state it is in (unless you like to live dangerously and change globes in lights that may be still on :-) ).
Yes, it's fine for Year 12 - you've already learnt all that stuff by then - it's NOT fine for Year 7 as a first proper programming language, when they haven't learnt ANY of that stuff yet.