sorry for the stupid question, how to run the application with the system? like a autorun on Windows [import]uid: 126133 topic_id: 31853 reply_id: 331853[/import]
Do you mean start Corona SDK when your system boots or do you mean to have your app auto start on a device.
Auto start on a device is not possible unless you’re apple or google…
If you want it to start on your Mac when it boots up, google “Mac startup items” and that should get you started. On windows I think it still uses autoexec.bat as well as msconfig to pick things to start at boot time. [import]uid: 19626 topic_id: 31853 reply_id: 127109[/import]
thx very much , I mean auto start on a device [import]uid: 126133 topic_id: 31853 reply_id: 127115[/import]
Mobile devices don’t give developers access to auto run things for a couple of reasons. For the most part, apps do not run in the background unless it’s some system daemon. Background apps suck battery power and with the limited screen real estate, users really can only use one app at a time, so unless you’re working for the OS maker, access to things that start up and run in the background are not allowed.
The 2nd main reason is security. Auto-run is how viruses, malware and other evil things get into peoples computers. I would not want to power up my phone and have your app take over. No mobile OS vendor is going to permit this behavior.
Finally most people don’t power off their devices unless they have to reboot for some reason or if they are flying and follow the rules of actually powering off their devices (you would be surprised at how many people actually ignore that directive and just sleep the device…) When would you actually auto-run your app? (since the phone is already up and running). Waking from sleep pretty much resumes the last foreground app that was running unless it’s been programmed to exit on suspend.
[import]uid: 19626 topic_id: 31853 reply_id: 127135[/import]
Do you mean start Corona SDK when your system boots or do you mean to have your app auto start on a device.
Auto start on a device is not possible unless you’re apple or google…
If you want it to start on your Mac when it boots up, google “Mac startup items” and that should get you started. On windows I think it still uses autoexec.bat as well as msconfig to pick things to start at boot time. [import]uid: 19626 topic_id: 31853 reply_id: 127109[/import]
thx very much , I mean auto start on a device [import]uid: 126133 topic_id: 31853 reply_id: 127115[/import]
Mobile devices don’t give developers access to auto run things for a couple of reasons. For the most part, apps do not run in the background unless it’s some system daemon. Background apps suck battery power and with the limited screen real estate, users really can only use one app at a time, so unless you’re working for the OS maker, access to things that start up and run in the background are not allowed.
The 2nd main reason is security. Auto-run is how viruses, malware and other evil things get into peoples computers. I would not want to power up my phone and have your app take over. No mobile OS vendor is going to permit this behavior.
Finally most people don’t power off their devices unless they have to reboot for some reason or if they are flying and follow the rules of actually powering off their devices (you would be surprised at how many people actually ignore that directive and just sleep the device…) When would you actually auto-run your app? (since the phone is already up and running). Waking from sleep pretty much resumes the last foreground app that was running unless it’s been programmed to exit on suspend.
[import]uid: 19626 topic_id: 31853 reply_id: 127135[/import]
I had no idea that malware enter computers through auto-runs. It does make sense though, every time I had suffered this kind of targeted attacks, it happened after running the executable for some program. Surely, scanning the files before installing them could have saved me of a lot of trouble…
[import]uid: 220227 topic_id: 31853 reply_id: 140904[/import]
I had no idea that malware enter computers through auto-runs. It does make sense though, every time I had suffered this kind of targeted attacks, it happened after running the executable for some program. Surely, scanning the files before installing them could have saved me of a lot of trouble…
[import]uid: 220227 topic_id: 31853 reply_id: 140904[/import]