Your quick fix worked well but it did break the code. We wouldn't expect "second" on the first line of our xml. I wonder if there is any better solution? Like declaring all of our elements before hand and re-use them later.
I am trying to do this aligning with two other layouts(grid and linear) inside the relative one, but I dont seem to have the attributes for the specific layout - do you know why this happens?
There was some weird bug involved with it- it always activated the previously written layout's attributes and woudnt allow either of them to work (errors and such). After a few clean and rebuild of solution and restart of VS, it seemed to have fixed by itself. Very weird bugs though
Hi Reso Coder. First of all, thank you so MUCH for your great tutorials !! They're the best on the whole net !! I'm learning sooooo much with them. Now, just a question : do you mean XAMARIN ANDROID is buggy too ? ( I abandoned XAMARIN FORMS for this precise same reason, and hoped to solve using XAMARIN ANDROID ). So, at last, you switched to native JAVA development ?
Yes, it is buggy. It's not that you cannot develop in it but native development will save you much time and despair. (Also I recommend Kotlin over Java 😉)
Your quick fix worked well but it did break the code. We wouldn't expect "second" on the first line of our xml. I wonder if there is any better solution? Like declaring all of our elements before hand and re-use them later.
I am trying to do this aligning with two other layouts(grid and linear) inside the relative one, but I dont seem to have the attributes for the specific layout - do you know why this happens?
Do you mean you can't do stuff with the grid and linear layout? Like "android:orientation"... If so, it must be a bug inside Xamarin :/
There was some weird bug involved with it- it always activated the previously written layout's attributes and woudnt allow either of them to work (errors and such). After a few clean and rebuild of solution and restart of VS, it seemed to have fixed by itself. Very weird bugs though
Xamarin is buggy as hell. That's the main reason why I switched to native development on Android.
Hi Reso Coder. First of all, thank you so MUCH for your great tutorials !! They're the best on the whole net !! I'm learning sooooo much with them. Now, just a question : do you mean XAMARIN ANDROID is buggy too ? ( I abandoned XAMARIN FORMS for this precise same reason, and hoped to solve using XAMARIN ANDROID ). So, at last, you switched to native JAVA development ?
Yes, it is buggy. It's not that you cannot develop in it but native development will save you much time and despair. (Also I recommend Kotlin over Java 😉)
you are best teacher'
Thanks you Sir. Your Video was very good
You are the best
good video, thanks a lot along with the code
Thank you for watching!
Great 👍
Like like like⭐️⭐️⭐️