fix: using example

Author: Kaushik Gopal

app/src/main/kotlin/com/morihacky/android/rxjava/fragments/UsingFragment.kt

@@ -15,7 +15,6 @@ import io.reactivex.Flowable
 import io.reactivex.functions.Consumer
 import io.reactivex.functions.Function
 import org.reactivestreams.Publisher
-import timber.log.Timber
 import java.util.*
 import java.util.concurrent.Callable
 
@@ -58,16 +57,16 @@ class UsingFragment : BaseFragment() {
 
     inner class Realm {
         init {
-            Timber.d("--- initializing Realm instance")
+            _log("initializing Realm instance")
         }
 
         fun doSomething() {
-            Timber.d("--- do something with Realm instance")
+            _log("do something with Realm instance")
         }
 
         fun clear() {
             // notice how this is called even before you manually "dispose"
-            Timber.d("--- cleaning up the resources (happens before a manual 'dispose'")
+            _log("cleaning up the resources (happens before a manual 'dispose'")
         }
     }
 

app/src/main/res/values/strings.xml

@@ -42,7 +42,7 @@
     <string name="msg_demo_timing">BTN 1: run single task once (after 2s complete)\nBTN 2: run task every 1s (start delay of 1s) toggle \nBTN 3: run task every 1s (start immediately) toggle \nBTN 4: run task 5 times every 3s (then complete) \nBTN 5: run task A, pause for sometime, then proceed with Task B</string>
     <string name="msg_demo_rotation_persist">This is an example of starting an Observable and using the result across rotations. There are many ways to do this, we use a retained fragment in this example</string>
     <string name="msg_demo_network_detector">This is a demo of how to use Subjects to detect Network connectivity\nToggle your Wifi/Network on or off and notice the logs</string>
-    <string name="msg_demo_using">This is a demo of the somewhat unknown operator "using".\n\nmsg_demo_usingYou typically use it for managing setup/teardown of resources. Classic cases are DB connections (like Realm), sockets, locks etc.\n\nTap the button and look at the logcat. Particularly notice how the Realm instance is self-contained. That is, it is auto-disposed right after use.</string>
+    <string name="msg_demo_using">This is a demo of the somewhat unknown operator "using".\n\nYou typically use it for managing setup/teardown of resources. Classic cases are DB connections (like Realm), sockets, locks etc.\n\nTap the button and look at the logcat. Particularly notice how the Realm instance is self-contained. That is, it is auto-disposed right after use.</string>
     <string name="msg_demo_multicast_publishRefCount">RefCount starts the upstream right away and gets disposed off, when all subscribers stop. Hit S1, Hit S2, Hit S1, Hit S2. Hit S1/S2 now and notice the stream starts all over.</string>
     <string name="msg_demo_multicast_publishAutoConnect">AutoConnect(2) waits for a min. subscriber count, before starting the upstream. Hit S1 (notice events don\'t start), Hit S2 (notice events now start), Hit S1 (notice that unsubscribing doesn\'t affect upstream), Hit S2, wait for sometime and hit S1 again (notice source stream doesn\'t restart)</string>
     <string name="msg_demo_multicast_replayAutoConnect">Replay caches the last item. Hit S1, Hit S2, event starts, Hit S2, wait a bit, Hit S2 again (notice it starts with the last item that S1 saw - courtesy Replay). Hit S2, Hit S1, wait a bit. Hit S1 again (notice event upstream continues and doesn\'t restart)</string>