LoadCod will load the application onto the simulator, but will not actually launch the application. To do this, you still have to manually start it, passing the keyboard, trackball or touch events to click the application icon (again using the fledgecontroller). In addition, you can try to configure the loading of the application at startup (this is a flag in the application descriptor file); but whether this will work will depend on what your application does.
As I do this, I need to pre-configure the simulator session by hiding all other applications / icons in the home folder. Then, when the cod loads, it will be the only application, so you can just send a click event to fire it. But if you want to be more thorough, you will also have to send a trackball or keyboard events to select an application.
The only way to pass the parameter to the application is to set the parameter value in the application descriptor file (which is included at compile time). If you need some parameter to indicate that it should be an instance for testing, you can compile two versions - one for production, which does not have a set of parameters, and the other for testing. Then you just download the test version via fledgecontroller.
If you haven’t downloaded the application to the simulator at all, you can also try replacing the \\ characters with / characters (I think the fledgecontroller deals with the slash, as a rule, inside as well, I’m not sure, because its obviously a Windows program, but there you have it ...)
source share