Thread: nativeBridge.dbgCmd
View Single Post
Old 03-15-2012, 12:05 PM   #20
thatworkshop
hub
thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.thatworkshop ought to be getting tired of karma fortunes by now.
 
thatworkshop's Avatar
 
Posts: 715
Karma: 2151032
Join Date: Jan 2012
Location: Iranian in Canada
Device: K3G, DXG, Kobo mini
Quote:
Originally Posted by JustAMan View Post
Then maybe there's no need to kill itself? Let this WAF app live till another WAF starts...
For browser it makes sense, I like to be able to see the last page I looked at... but for other WAF apps, I think their processes should be killed as soon as back button is pressed! I don't like to have their processes running till next WAF kicks in.

Does anyone know how to revert it back so that nativeBridge.dbgCmd() can work?
Last edited by thatworkshop; 03-15-2012 at 12:35 PM.
thatworkshop is offline   Reply With Quote