티스토리 뷰
Manifest
1. supportsRtl
developer.android.com/guide/topics/manifest/application-element?hl=ko#allowbackup
android:supportsRtl="true"
이슬람 문화권에서는 레이아웃의 방향이 서구문화권과는 반대이기 때문에
안드로이드 SDK 버전 17이상에서는 운영체제 차원에서 RTL(Right-TO-LEFT) 레이아웃을 지원한다는 얘기.
It gives you RTL support which means mirror effect for devices have local languages orientation from right to left, such as Arabic, Persian etc.
targetSdkVersion이 17이상이 아니라면 아무 쓸데없는 옵션이다.
Declares whether your application is willing to support right-to-left (RTL) layouts. If set to true and targetSdkVersion is set to 17 or higher, various RTL APIs will be activated and used by the system so your app can display RTL layouts. If set to false or if targetSdkVersion is set to 16 or lower, the RTL APIs will be ignored or will have no effect and your app will behave the same regardless of the layout direction associated to the user's Locale choice (your layouts will always be left-to-right).
The default value of this attribute is false.
This attribute was added in API level 17.
if you are building an app in Arabic, Urdu, Hebrew, etc... or any language that is written from right to left you should set android:supportsRtl to true, that's how you tell the layout to be from right to left, and The default value of this attribute is false.
stackoverflow.com/questions/41939948/what-is-androidsupportsrtl-attribute-in-androidmanifest
출처: https://allwork.tistory.com/176 [100 Works]
2. screenOrientation
android:screenOrientation="sensorPortrait"
portrait - 세로 고정
sensor portrait - 세로방향 고정, 센서에 따라 정/역방향
[Android] 액티비티 화면 방향 설정
[Android] 액티비티 화면 방향 설정 액티비티 화면은 크게 생각하면 "가로" , "세로" 두가지로 되어있고 폰을 360도 회전한다고 생각했을때 총 4가지의 방향이 있습니다. 보통 매니페스트에서 액티비
necos.tistory.com
developer.android.com/guide/topics/manifest/activity-element.html?hl=ko
<액티비티> | Android 개발자 | Android Developers
Declares an activity (an Activity subclass) that implements part of the application's visual user interface. All activities must be represented by {@code } elements in the manifest file. Any that are not declared there will not be seen by the system…
developer.android.com
Log.d / Trace.d
Logging is not Tracing!
Logging:
When you design a big application, you need to have good and flexible error reporting - perhaps across machines - to collect log data in a centralized way. That is a perfect use case for the Logging Application Block where you configure some remote trace listener, and send the log data to a central log server which stores its log messages in a database, log file or whatever. If you use out-of-process communication, you are limited by the network performance already, which in the best case is several thousand logs/s.
Tracing:
Besides Error Reporting, you also need to trace your program flow to find out where the performance bottlenecks are; even more importantly, when an error occurs, you have a chance to find out how you did get there. In an ideal world, every function would have some tracing enabled with the function duration, passed parameters, and how far you did get into your function.
더블클릭되는것 막기
유저가 빠르게 여러번눌러서 처리 큐에 같은 이벤트가 중복으로 들어가는 경우 방지하기
stackoverflow.com/questions/5608720/android-preventing-double-click-on-a-button
Android Preventing Double Click On A Button
What is the best way to prevent double clicks on a button in Android?
stackoverflow.com
- Total
- Today
- Yesterday
- 시뮬레이터 키보드
- 백준 1644
- 백준알고리즘
- 파이썬 최대공약수
- 카카오 기출
- 데이터바인딩 뷰바인딩 차이
- 코틀린 데이터바인딩
- 코틀린 뷰바인딩
- 카카오 키해시
- 코틀린 뷰페이저
- 프로그래머스
- 안드로이드 키해시
- 백준
- 코틀린
- TextFormField keyboard
- 투포인터 알고리즘
- 안드로이드
- 코틀린 바텀네비게이션
- 안드로이드 카카오톡으로 로그인
- 투포인터 알고리즘 파이썬
- 소수 구하기 파이썬
- kotlin fragment
- counting sort
- 백준 2003
- 전화번호목록 파이썬
- 코틀린 리스트뷰
- 카카오톡으로 로그인 오류
- flutter simultor
- 백준 1806
- Kotlin
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 |