ITBLogs.InfoGoogle Oct 4 Update
Recently, I read some advertisements from Google; they will have some important announcements on that day. I have no insiders' information. I just can guess what will happen. I think the Pixel Phone will be announced. The rumors about this phone are circulated on the internet for months. That will be the new brand of the flagship phone for Google; they will phase out Nexus series. That makes sense; recently Apple released their new phone, iPhone 7. Google needs to release their new phone as a response. I am looking for that; that may be my next development phone. Also, I guess there will be some information about the next version of Android.
Loading Images from Xamarin Forms
Even the UI I built is very simple; I need to load some icons in the UI. I have used navigation page. After I had navigated two pages, then I got an exception, OutOfMemoryException. That is because Bitmap Decode is used a lot of memory. I found we should avoid using:
Code
img.Source = ImageSource.FromFile("test.jpg"); |
We should use the images in the embedded resources
Code
img.Source = ImageSource.FromResource("advgen.test.jpg"); |
Please change the properties of the image file:
Then the problem will solve.
SMS is popular in Australia
I got a lot of friends in Hong Kong. They are very very rare to use SMS now. The most of them are using WeChat, Line, WhatsApp, those of IM to communicate. That is because IM is free and SMS need to be charged. In contrast, most of my friends in Australia is still very popular to use SMS. I think that is because most of the phone plans come with unlimited SMS. Sending SMS is the core feature of a mobile phone; you do not need to install any app. It won't slow your phone too. For them, that is a better option to use SMS.
Keeping the FAB Button at right bottom side
I put every fragment with their own FAB Button. I found that is always placed under the last element of that layout. It won't be pushed further bottom, at the right bottom of the screen. I used to use the LinearLayout and RelativeLayout, they won't work too.
FInally, I found android.support.design.widget.CoordinatorLayout is only way to work, I don't know why yet, I found this solution by trial and error
Code
<android.support.design.widget.CoordinatorLayout | |
android:id="@+id/rootLayout" | |
android:layout_width="match_parent" | |
android:layout_height="match_parent"> | |
<android.support.design.widget.FloatingActionButton android:id="@+id/fab" | |
android:layout_width="wrap_content" android:layout_height="wrap_content" | |
android:layout_gravity="bottom|end" android:layout_margin="@dimen/fab_margin" | |
android:src="@android:drawable/ic_input_add" /> | |
</android.support.design.widget.CoordinatorLayout> |
Outlook not working, staying in "prcoessing..."
Yesterday, I found my Outlook is not working anymore. I cannot open it! It stayed in a splash screen,the "processing..." wordings is staying in there. After I did some researches and testing, I found the root cause is from the COM Add-ins for Outlook. To solve this problem, you need to go into the safe mode of outlook, you just need to type "outlook /safe" in "Run...." or command prompt. After you enter safe mode, you need to File->Options->Add-ins->COM-Add-ins->Go
Then you checked all add-ins you do not need to use. Finally, you close your outlook, open it in normal mode again. It will work again.