I don't know if anyone else has experienced this, i've been looking for examples left, right and centre to no avail.
Anyway, i'm developing an app using Xamarin forms for ios, android and windows phone. The first page of the app is a tabbed page and the first content page consists of a listview with an image (with the source bound to a string with a url) and some labels. I get the data via binding and everything loads correctly except the images. However, when i open a new page and then go back to the tabbed page, the images suddenly appear. I'm testing on a Windows Phone 8.1 at the moment.
Anybody else experienced this? Any work arounds? Any help would be much appreciated.
This might be caused by a known issue that was fixed in 2.2.0-pre1
https://bugzilla.xamarin.com/show_bug.cgi?id=39447
Try updating to that pre-release version and seeing if it resolves your issue.
Related
I haven't noticed this before, so it may be a bug with the new release.
When I click on a NavigationLink, everything works as expected. Then I can click the back button (which I have done with the default back button as well as a custom back button) and it still works. If I try to click the same NavigationLink again, it does not trigger the destination. I can click on a different NavigationLink, and it will work, and when I go back the first link is functional again. Only the last link is unavailable.
This seems to be the case in lists, forms, and free navigation links.
Has anyone encountered this functionality? Is there a fix for it?
Working on Xcode Version 11.3 (11C29)
Thank you for your help.
After a lot of searching and testing, this appears to be a bug specific to the simulator in the new release. When running the app on my phone it works perfectly. Hopefully it is fixed soon, but for now I can run testing on the phone.
I have created a Cross platform application to create an android application. In Main page I have a toolbar and listview that lists the data from sqlite database. it was working all well and now when I am trying to do change to the same screen to add some more controls, its not working when I run the project to debug. New controls are not visible on the screen. Its always showing the old screen as it is.
i don't have the rep to comment, but I've found that kind of scenario often with Android.
Changing UI components don't update.
When I do UI changes I'll often uninstall the app off the Android first, as the most reliable way, as I'm sure I've done the "clean solution", delete bin/obj folders and still had issues with the app on the droid not being fully updated to the new UI.
On the website: www.onlineskateschool.com the links work fine on desktops, but when you go to a mobile device, none of the links work.
I have tried a few different versions of bootstrap, but this has not helped yet. Any ideas where my issue could be?
This can be replicated in Chrome Canary on a desktop with the 'nexus 5' selected after pressing f12 for developer tools.
It seems like your javascript with your auto reformatting of the menu links is your culprit. The phone's width is too big to change to the mobile menu (3 barred icon that contains the links which work on mobile) but it is too small to work on the original links (the ones you see on a regular desktop). Try resizing your browser's width and you will see what I am talking about.
You should change the js code that has to do with your reformatting and then your links should work.
I am trying to find the difference between the uses of a basic page and a blank page on windows store apps. I am writing an application that has multiple pages and I am not sure which one to use for my main page and I can't seem to find an answer that is helpful.
Basic Page inherits Common.LayoutAwarePage. This gives your page various capabilities like the automatic back button and a visualstatemanager for snapping among other things.
Blank Page only inherits Page and does not get any of the above capabilities. So for example if you need to incorporate snapped view in your page, you need to add a handler for the size changed event in your code.
A Basic Page makes it very easy to just write all the snapped changes in your VisualStateManager in XAML and then test it without running your code using just the device tab where you can select state of your device.
The MainPage in your project is a Blank Page and I prefer to create all other pages as Basic Pages to not worry about stuff like the back button.
That being said, Windows 8.1 apps do not include the LayoutAwarePage so if you are not used to the LayoutAwarePage, do not bother.
Let me know if you need more clarification.
Go with the Basic Page as it gives you automatic back button your view's title etc, and if you don't need them you can disable them also. But for blank page you have to write code for those common things.
This blog post will help you in understanding of Basic Page vs Blank Page.
http://myblogwindow8.blogspot.com/2013/06/blank-page-vs-basic-page-template.html
I have started creating a custom button for Picasa to be able to upload some photos to a website. I followed the guidance found here. It works fine so far but now I have made a small change to the button and picasa will not refresh the button no matter what I try.
Adding a link like this:
Acme Inc. Uploader
to a page with access to your PBZ file will cause Picasa to open and instal the button. I made a small change and tried again. It updated once but now it refuses. I tried changing the name of the button, the version of the button, nothing works. Only the original button remains in Picasa. I even remove the button from picasa, reboot just in case its in memory somewhere, then tried again and still only original button remain.
The google group associated with the API does not appear to be very active. One other person asked about the same thing but there was no response. Searching the web found no other answers. I hope someone here has some experience with this.
I found a buttons folder in the picasa folder on the hard drive but my custom button was not in there. I have no idea why it keeps finding the old button.
I am using Picasa 3.1.0 on Windows XP if that makes any difference.
So the question: does anybody have experience building these custom buttons and/or encountered this situation before?
Thanks