|
|
Robert Nadler wrote: I wish I had that much spare time!
You already have enough mobile phones?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
That's fake. No one has that many cell phones.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
|
I was doing it at my previous work.
Every now and then Xamarin will have build issues and it was particularly painful with the Mac. Frankly I suspect it's the Max development constraints at work here, not Xamarin which is the issue.
But most of the time it worked out well. Particularly when you consider what you are doing (multi target phone OSes)
|
|
|
|
|
Super Lloyd wrote: Particularly when you consider what you are doing (multi target phone OSes)
I do agree with that. It is amazing that they have gotten all this to work at all.
It's just annoying when things partially and/or intermittently work.
And, I must admit it was very cool to get that default app running on all three platforms (win10, ios, android).
Wow. Once it works (if it does) it almost makes you forget the pain. Almost.
|
|
|
|
|
raddevus wrote: Because no one really cares about Microsoft and/or Xamarin. Thats true, kindof. Why invest time in something that they are going to drop again? By the time they get the problems sorted out, they already plan to get rid of it. I think it's easier to get rid of them.
|
|
|
|
|
What makes you say they plan to get rid of it? Is there an article someplace that you read that you could provide the link to?
|
|
|
|
|
CodeWraith wrote: Why invest time in something that they are going to drop again?
I know, right. We all feel like that out here. So many technologies that Microsoft has done that way.
It was really shocking when the Silverlight stuff just disappeared over night.
|
|
|
|
|
I've been programming in Xamarin for several months. I experienced the problem you are referring to a couple of times early on. What I learned is that it is pretty picky about the versions running on both machines. If you update Xamarin for VS, then there is most likely an update that needs to be applied on the MAC side(Xcode). Keep everything up to date and you should be good. The other thing I did that also helped was to switch the MAC over from WiFi to hardwired and switched the dynamic IP to static.
|
|
|
|
|
Thanks. I will keep those tips in mind.
littleGreenDude wrote: The other thing I did that also helped was to switch the MAC over from WiFi to hardwired and switched the dynamic IP to static.
My Mac is headless so all my work was across network via VNC and early on I was in such pain over WiFi that I implemented a hardwired solution too.
|
|
|
|
|
Some of my coworkers do a lot of Xamarin work. They've had enough issues with the remote mac that they recommend doing anything IOS related on the Mac directly instead.
PS They also say trying to customize the UI in Xamarin.Forms (the cross platform UI library) is nearly impossible and that for anything beyond a "don't care what exactly it looks like line of business app", you're better off making the UI a dumb presentation layer and using Xamarin.Ios and Xamarin.Android to create separate native UIs for each version of the app because it's less work overall and you don't have to argue with the customer about how [Insert Trivial UI Thing Here] is actually a 5 or 10 days of work not 5 or 10 minutes.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Thanks, great comments.
Dan Neely wrote: they recommend doing anything IOS related on the Mac directly instead
I was looking at that option also. I fired up VSTudio on the Mac. The pain of that is almost like learning an entirely new IDE though. I'm a PC not a Mac so I have more barriers to entry.
Dan Neely wrote: They also say trying to customize the UI in Xamarin.Forms (the cross platform UI library) is nearly impossible
This is exactly why I was trying this Cross platform thing in the first place. This is exactly what I thought too. This cross-platform solution seems like a dog and pony show to me. It all looks good but when you go to dev real apps then look out, you are going to suffer.
Since I've actually developed a specific app natively on Win10 (as Winform and Universal Windows App), Android and iOS I was wondering if Xamarin could actually make things faster. I'm thinking that for most apps (except the most basic) it is just easier to use good solid OOP practices (SoC, MVC, Data Models, etc) and create each one natively.
When I created the app that was on all platforms (see it on Google Play : C'YaPass Never memorize a pwd again[^] ) I found that I had to change very little actual code.
It was the UI stuff that you had to customize. But if you have to do that in Xamarin then you get nothing really.
|
|
|
|
|
Data layer, business logic, and network code are all still sharable. IIRC being told by coworkers that a 2/3rds shared code base is typical. That'd put the notional overhead for writing 2 UIs as 20% (4 parts shared and 1 part first platform UI, with 1 part second platform UI as the overhead) above a cross platform layer that fully delivered. In the usual case where your client isn't sure exactly what they want its generally less if you can initially only do 1 platform until they've seen a nearly complete app long enough to actually make up their minds because as a port without all the intermediate design steps platform #2 should take less work to finish.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
So my mouse cursor vanished. Gone. Nowhere to be found. Now all I have is a keyboard to navigate with. On Windows 10. Not fun. I was cursing MS even though it was probably me doing something dumb. Yes, ok, it was me. I have no idea what I did but I did it.
Anyway, after quite a while of head scratching I decided to reinstall windows. I fired up Rufus, pointed it to an iso and hot start (I have another old machine which is still usable in an emergency and I'm pretty sure this qualified).
It was almost done when I thought, "System restore!" Never had to use it before so took a bit of fiddling with the keyboard to get it up and let it do it's thing.
And by golly, it did. Cursor back. Hurrah for MS, boo to me.
ps this wasn't much of a rant more of a phew!
|
|
|
|
|
I'm sitting here wondering why your mouse cursor disappeared?
And hoping this isn't The Next Big Thing on Win10.
|
|
|
|
|
Perhaps something like disabling the mouse and using a touchscreeen, no matter wether you have one or not?
|
|
|
|
|
CodeWraith wrote: disabling the mouse and using a touchscreeen, no matter wether you have one or not
Ah, yes, that's a good guess. Hadn't thought of that one. You're probably right.
|
|
|
|
|
No idea. All the drivers were where they should have been. Restarted a couple of times, updated/re-installed the drivers (which isn't easy with only the keyboard!). Nada, zip, zero, nothing. The touchpad is gone and pulling the usb stick for the mouse/keyboard does nothing. Note that the USB keyboard worked fine.
My though to reinstall was more of an opportunity to clean house and then it struck me to try a system restore. Worked like a charm. Hurray for MS!
|
|
|
|
|
My first thought was battery in the mouse has gone. My next thought was faaarrrkk he reinstalled Windows for a flat battery. And finally, bloody hell, reinstall/restore fixes flat batteries.
I really need to think beyond my horizon .
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Battery was only a few days old anyway and the touchpad wasn't working so not just the mouse at fault!
|
|
|
|
|
Without even a BAdunk sound and saying the device is unrecognized?
|
|
|
|
|
I have to assume you had restarted Windows, before concluding you had to reinstall it...?
If so, and the problem was still present...you could also have tried to get into the mouse control panel applet and assign something else to the pointer. I've seen that fix a similar problem.
Or try to remote into the machine from another one - I've also seen the new session get a new pointer, while it wasn't visible on the local machine.
Of course now you won't be able to test any of these...but hopefully you'll have a few ideas before if it ever happens again...
|
|
|
|
|
dandy72 wrote: I have to assume you had restarted Windows, before concluding you had to reinstall it...? Your assumption is correct - restart fixes almost everything!
dandy72 wrote: If so, and the problem was still present...you could also have tried to get into the mouse control panel applet and assign something else to the pointer. I've seen that fix a similar problem. Interesting - hadn't considered that.
dandy72 wrote: Or try to remote into the machine from another one - I've also seen the new session get a new pointer, while it wasn't visible on the local machine. Also interesting.
dandy72 wrote: Of course now you won't be able to test any of these...but hopefully you'll have a few ideas before if it ever happens again... Food for thought indeed. Thanks
|
|
|
|
|
I have occasionally seen that problem (though I don't think ever in Win 10). The mouse is still connected and working but there is no mouse cursor. My fix is simply to open a command prompt in full screen and then close it again.
Phil
The opinions expressed in this post are not necessarily those of the author, especially if you find them impolite, inaccurate or inflammatory.
|
|
|
|