Run APK
Kalipso - Form - Actions - Actions Description - Group Others - Run APK
Last updated
Was this helpful?
Kalipso - Form - Actions - Actions Description - Group Others - Run APK
Last updated
Was this helpful?
Executes a specified function on a specified APK or JAR file.
Action available for the following operating systems:
General
APK File <string> - Defines the full path and name of the APK or JAR file that contains the function to run. If LoadAPK Action hasn’t been called, Kalipso loads the APK, run this Action and then unloads the APK.
Class Name <string> - Fully classified class name that contains the function to execute.
Method Name <string> - Java Method name that you want to run. This method must be a static method.
Run Mode <numeric>
1- UI Thread In this case, the code is executed from the UI thread and you can invoke user interactive code directly.
2- Background Thread In this case, the code is executed in a background thread. If you need to invoke code in the UI thread you need to make the necessary UI thread invoke.
Return Type <string>
0 - Void
1 - Byte
2 - Short
3 - Int
4 - Long
5 - Float
6 - Double
21 - Char
22 - String
23 - Byte Array
Parameters
Type <Parameters Type>
0 - Void
1 - Byte
2 - Short
3 - Int
4 - Long
5 - Float
6 - Double
21 - Char
22 - String
23 - Byte Array
101 - Activity - This option will pass the current Kalipso Form associated Android Activity.
102 - View - This option allows you to select a Kalipso control and pass its top level Android View as a parameter.
103 - Kalipso DB Accessor - This option will pass a KDBAccessor interface implementation for the specified database profile. This interface will allow you to access the specified database.
104 - Android Context - Passes in a Context with assets/resources from the specified file (in this case it must be an APK file). This will be necessary if the APK uses its own resources.
105 - PostNotify Interface - This option will pass a KExternalEventsInterface implementation. You can use this to send notifications back to Kalipso if you have asynchronous code executing in the library, or for example a background thread that you leave running. This will allow you to invoke the "App Notified" event in forms an fill in Temporary variables from that event. This invocations you make to notify Kalipso are asynchronous, so the calls to this interface will return immediatly, and they return false if no Form was found to handle the notification. This also allows you to register for event notification callbacks, like OnActivityresult, AppPausing, AppResuming, Key releated events, etc.