Explore >> Select a destination
|
You are here 
|
zserge.com | ||
| | | | |
wittchen.io
|
|
| | | | | When we work with Activities in Android, defining different layouts for different screen orientations is easy. The only thing we need to do, is to create two *.xml files with the same name for layouts in two separate directories (res/layout/ and res/layout-land/). In Fragments its not that easy. In such case, we need to perform additional operations in order to achieve our goal. Fragment in Android is not re-inflated on configuration change, but we can recreate layout and repopulate view manually. | |
| | | | |
arpitonline.com
|
|
| | | | | In my previous post, I had written a bit about creating custom Layouts for Android. However to make a truly reusable layout there are a few more things we'd probably need: Some unique properties that you may want to assign to it via XML (Like LinearLayout has an orientation property unique to it) Custom LayoutParams... | |
| | | | |
ryanharter.com
|
|
| | | | | On a recent client app, I ran into a situation where I needed an arbitrary number of EditText fields based on a selected value, where the user could enter people's information. My initial thought was to put this logic in my Fragment, just adding EditTexts to a LinearLayout container as the selected value changes, but that bloated my Fragment, and didn't allow for much reuse. This was a perfect opportunity to encapsulate this interaction functionality in a custom view, which would be reusable throughout t... | |
| | | | |
10xlearner.com
|
|
| | | Hello ! I'm Xavier Jouvenot and here is the fourth part of a long series on The Modern C++ Challenge. In this article, I am going to explain how I solved the fourth problem in C++, and how I integrated the solution in an Android project. The objective of fourth third problem is simple. We... | ||
