I want to pass values to a Tasker variable (to be used by Zooper) when a folder opens and closes.
I want to pass values to a Tasker variable (to be used by Zooper) when a folder opens and closes.
Is this possible and if so any guidance?
Tried to search posts but G+ not so friendly.
]]>« Here’s some screenshots from PowerPoint to better help understand my “Color Scheme” suggestion. (Previous Post)
(Next Post) From another post: »
D5 Creation
< ![CDATA[
Theoretically yes, practically no.
The only thing you can pass is a toggle signal…
]]>
< ![CDATA[
Passing values… not sure. What should be possible is creating a shortcut to a Tasker Task and launch that as intent. However you cannot pass values. If it’s simple i.e. On/Off, you could create two tasks for that.
However: Even if it worked, be aware that ZW takes some time, many seconds possibly until changes appear in widgets. It seems ZW iterates through all widgets to find out which to update.
]]>
< ![CDATA[
Perhaps you can try to run a custom tasker shortcut that will change those variables in the open/close event of the folders.
(Don’t know tasker enough to suggest better solutions)
[ Lutz Linke, you were faster ]
]]>
< ![CDATA[
Lutz Linke I agree. The only problem I see is that it happens even with only one widget meaning the iteration is false. This is false because there’s no excuse for it to iterate anything if there is only one widget, it should just shut the hell up and update it. But even with one widget it takes a few second and I’ve had instances where it didn’t update at all.
]]>
< ![CDATA[
What exactly do you want to pass?
]]>
< ![CDATA[
Thanks guys. Maybe there’s a simpler way but I wanted to display the folders name in the main Zooper widget at the top of my display. I’ve used tasker a bit so seem logical to me.
]]>
< ![CDATA[
Pierre is going to hate me for this, but you can use the LL.writeToLogFile(string,false); combined with a tasker task reading the logfile to pass a string to tasker.
]]>
< ![CDATA[
Lukas Morawietz no problem 😉
Maybe have a look at this: http://tasker.dinglisch.net/invoketasks.html. This describe how to build an intent to trigger task execution. This is Tasker specific but it can easily be mapped to Intent methods available through scripting in LLX. (Sorry, not a full answer, but some hints only)
]]>
< ![CDATA[
Thanks Pierre.
I also found the Zooper dev said “you can actually send Tasker variables even without Tasker installed (this is what Media Utilities does), just send a Broadcast with “org.zooper.zw.action.TASKERVAR” action, add a Bundle to the intent as “org.zooper.zw.tasker.var.extra.BUNDLE” with “org.zooper.zw.tasker.var.extra.STRING_VAR” and “org.zooper.zw.tasker.var.extra.STRING_TEXT”.”
Is it possible to build and use the intent from a script and cut out Tasker? Might solve the refresh lag?
]]>
< ![CDATA[
Sorry for the delay. A the moment this could almost be done through script but one small piece is missing. This piece (the Bundle class) will be available in the next beta (I hope soon). Can you remind me about this conversation once the beta (or release) is out and I’ll provide you a script to do that.
]]>
< ![CDATA[
Pierre Hébert no problem I have spent some time getting to grips with sending intents in Tasker so no time wasted/lost. I will happily remind you when you update to include bundle class – need to sign up to beta
]]>
< ![CDATA[
Tony Merrell-Jones well hurry already hahahaha
]]>
< ![CDATA[
Curtis Sylvester Jr. Yeah got nervous when it said as it’s a beta it might contain bugs – made me smile 😉 Although having seen some posts not everyone gets it
]]>
< ![CDATA[
I’m kinda glad you took it as a joke because it was meant as such
]]>