java - Thread seems to magically start -


i have issue thread while working android studio. here thread class :

class mainloop extends thread {       private boolean run = true;      @override     public void run() {         system.out.println("thread started");         run = true;          final double spf = 1.0/2.0;         double deltas;         long lasttime = system.nanotime();         long newtime;          while(run) {             newtime = system.nanotime();             deltas = (float)(newtime-lasttime)/1000000000f;             if (deltas > spf) {                 lasttime = newtime;                 system.out.println("hello thread");             }         }         system.out.println("thread killed");     }      void kill() {         system.out.println("killing thread");         run = false;     }  }

and here mainactivity class :

    public class mainactivity extends appcompatactivity {           private mainloop mainloop = null;          @override         protected void oncreate(bundle savedinstancestate) {             super.oncreate(savedinstancestate);             mainloop = new mainloop();             mainloop.start();         }          @override         protected void onresume() {             super.onresume();             mainloop = new mainloop();             mainloop.start();         }          @override         public boolean ontouchevent(motionevent event) {             mainloop.kill();             return false;         }     }

and here output have :

08-15 12:24:07.480 2581-2667/com.lteii.hello i/system.out: hello thread 08-15 12:24:07.593 2581-2671/com.lteii.hello i/system.out: hello thread 08-15 12:24:07.595 2581-2581/com.lteii.hello d/viewrootimpl@e1e91f8[mainactivity]: viewpostimeinputstage processpointer 0 08-15 12:24:07.596 2581-2581/com.lteii.hello w/system: classloader referenced unknown path: /system/framework/qperformance.jar 08-15 12:24:07.597 2581-2581/com.lteii.hello e/boostframework: boostframework() : exception_1 = java.lang.classnotfoundexception: didn't find class "com.qualcomm.qti.performance" on path: dexpathlist[[],nativelibrarydirectories=[/system/lib, /vendor/lib]] 08-15 12:24:07.597 2581-2581/com.lteii.hello v/boostframework: boostframework() : mperf = null 08-15 12:24:07.598 2581-2581/com.lteii.hello i/system.out: killing thread 08-15 12:24:07.598 2581-2671/com.lteii.hello i/system.out: thread killed 08-15 12:24:07.622 2581-2581/com.lteii.hello i/system.out: killing thread 08-15 12:24:07.724 2581-2581/com.lteii.hello i/system.out: killing thread 08-15 12:24:07.746 2581-2581/com.lteii.hello i/system.out: killing thread 08-15 12:24:07.758 2581-2581/com.lteii.hello i/system.out: killing thread 08-15 12:24:07.760 2581-2581/com.lteii.hello d/viewrootimpl@e1e91f8[mainactivity]: viewpostimeinputstage processpointer 1 08-15 12:24:07.760 2581-2581/com.lteii.hello i/system.out: killing thread 08-15 12:24:07.980 2581-2667/com.lteii.hello i/system.out: hello thread 08-15 12:24:08.480 2581-2667/com.lteii.hello i/system.out: hello thread

i don't understand how possible, apparently onresume() method restarts thread everytime kill ontouchevent() method, since when delete onresume(), don't see anymore "hello thread" after "thread killed" anyway should see "thread created" between "thread killed" , "hello thread" need help!

try following:

public class mainactivity extends appcompatactivity {      private mainloop mainloop = null;      @override     protected void oncreate(bundle savedinstancestate) {         super.oncreate(savedinstancestate);         if (mainloop == null) {             mainloop = new mainloop();             mainloop.start();         } else {             system.out.println("oncreate: thread has not been killed!");         }      }      @override     protected void onresume() {         super.onresume();         if (mainloop == null) {             mainloop = new mainloop();             mainloop.start();         } else {             system.out.println("onresume: thread has not been killed!");         }      }      @override     public boolean ontouchevent(motionevent event) {         if (mainloop != null) {             mainloop.kill();             mainloop = null;         } else {             system.out.println("ontouchevent: thread has not been created!");         }         return false;     }

that should explain issue. in general practice double-check own code. in best case double-checks never called, in worst case know why things going wrong.

as side-note: thread created runs in infinite loop, drain battery fast doing nothing. @ minimum use thread.sleep or better use scheduledexecutor, or timer if ever have 1 thread.


Comments

Post a Comment

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

i'm implementing inapp billing in android app. works well, however, i'm trying decouple broadcast receiver activity manifest. suggestion in android's trivialdrive sample: // important: dynamically register broadcast messages updated purchases. // register receiver here instead of <receiver> in manifest // because call getpurchases() @ startup, therefore can ignore // broadcasts sent while app isn't running. // note: registering listener in activity bad idea, done here // because sample. regardless, receiver must registered after // iabhelper setup, before first call getpurchases(). currently there's class extends broadcastreceiver : public class iabbroadcastreceiver extends broadcastreceiver { /** * intent action receiver should filter for. */ public static final string action = "com.android.vending.billing.purchases_updated"; private final iabbroadcastlistener mlistener; public iabbroadcastreceiver(iabbroadcastlistener listener) { m...
Read more

python Tkinter Capturing keyboard events save as one single string -

is possible store keyboard events 1 string? code below stores 1 char , prints it. card reader or bar code reader, contains collection of character/ string not 1 character @ time. goal save char pressed text variable. from tkinter import * root = tk() def key(event): text= event.char text+= event.char print ("pressed", text) def callback(event): frame.focus_set() print ("clicked at", event.x, event.y) frame = frame(root, width=100, height=100) frame.bind("<key>", key) frame.bind("<button-1>", callback) frame.pack() root.mainloop() currently, creating text variable , everytime key() function gets called, , text stores last character typed. you can define text module level variable , , use module level text inside key function - text = '' def key(event): global text text+= event.char print("pressed", text)
Read more

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -

here tables: create table customer ( cid int primary key, name varchar(32) ) create table ord ( oid int primary key, cid int foreign key references customer, address varchar(20) ) here's linq-to-sql statement: var aaa = c in db.customer select new { c, o = c.ord.tolist() }; and here's inexplicable query generated linq-to-sql: select [t0].[cid] [cid], [t0].[name] [name], [t1].[oid] [oid], [t1].[cid] [cid2], [t1].[address] [address], (select count(*) [dbo].[ord] [t2] [t2].[cid] = [t0].[cid]) [value] [dbo].[customer] [t0] left outer join [dbo].[ord] [t1] on [t1].[cid] = [t0].[cid] order [t0].[cid], [t1].[oid] i want understand how rid of count(*) part. it's entirely uncalled for! linq needs count(*) in order determine number of entries returned o = c.ord.tolist() .
Read more