A feature I'd love to have (that's also a current roadblock I'm experiencing) is being able to set a custom key to send a custom intent.
Esentially, the use case I was trying to achieve, was sending an intent for the app Macrodroid to intercept. Naturally, it could be far more useful in all manner of other apps, too.
Having a basic look, it seems there may be some partial code for custom intents (variables for "SEND_INTENT_ONE", "...TWO" & "...THREE"). However, they don't quite look "plugged in" as I can't see code for setting them or for when they're executed. I could be completely wrong here though as I'm probably whatever level is below beginner for Android development ha.
Thanks for your time, it is much appreciated.
Take care 🙂!
EDIT:
Ok so I've figured out that using the intent key codes already in LeanType's code (i.e. -20000, -20001 & -20002), it does send an intent via IntentUtils' handleSendIntentKey(params). Passing the "EXTRA_NUMBER" constant as an extra of the intent. These can already be intercepted by Macrodroid/Tasker/+ apps successfully.
So, to be really beneficial, I think it would need:
-
Option in settings to add/remove/edit/view custom user definable intents. Otherwise it is limited to the 3 currently hardcoded intents, being "SEND_INTENT_ONE", "SEND_INTENT_TWO" & "SEND_INTENT_THREE".
-
Option in settings of each intent to set value(s) the intent passes as extras.
-
So that users could add these to a layout's JSON, some way to show the key codes of each custom intent would be needed. For context, currently the keycode for "SEND_INTENT_THREE" = -20002. However, being user defined, "USER_NAMED_INTENT_10" may be added with code -20009, or "USER_NAMED_INTENT_12" = -20011 etc. Maybe show codes next to the name of each intent (tabular display?).
Hope I've explained it with adequate sense.
A feature I'd love to have (that's also a current roadblock I'm experiencing) is being able to set a custom key to send a custom intent.
Esentially, the use case I was trying to achieve, was sending an intent for the app Macrodroid to intercept. Naturally, it could be far more useful in all manner of other apps, too.
Having a basic look, it seems there may be some partial code for custom intents (variables for "SEND_INTENT_ONE", "...TWO" & "...THREE"). However, they don't quite look "plugged in" as I can't see code for setting them or for when they're executed. I could be completely wrong here though as I'm probably whatever level is below beginner for Android development ha.
Thanks for your time, it is much appreciated.
Take care 🙂!
EDIT:
Ok so I've figured out that using the intent key codes already in LeanType's code (i.e. -20000, -20001 & -20002), it does send an intent via IntentUtils' handleSendIntentKey(params). Passing the "EXTRA_NUMBER" constant as an extra of the intent. These can already be intercepted by Macrodroid/Tasker/+ apps successfully.
So, to be really beneficial, I think it would need:
Option in settings to add/remove/edit/view custom user definable intents. Otherwise it is limited to the 3 currently hardcoded intents, being "SEND_INTENT_ONE", "SEND_INTENT_TWO" & "SEND_INTENT_THREE".
Option in settings of each intent to set value(s) the intent passes as extras.
So that users could add these to a layout's JSON, some way to show the key codes of each custom intent would be needed. For context, currently the keycode for "SEND_INTENT_THREE" = -20002. However, being user defined, "USER_NAMED_INTENT_10" may be added with code -20009, or "USER_NAMED_INTENT_12" = -20011 etc. Maybe show codes next to the name of each intent (tabular display?).
Hope I've explained it with adequate sense.